Slow Keychain on 2016 Macbook Pro with Touch Bar

I just updated to 10.12.4 - no change whatsoever. I still get the spinner whenever a password input form appears in safari and keychain remains as unusable as before the update. It is frustrating, first time I wishes I did not update to the latest hardware.

I still think it's a software issue. While experiencing the slow keychain lookup, if you look at Activity Monitor, you'll see that "secd" process is getting high CPU usage. The "secd" process seems to be responsible for iCloud keychain syncing.

High CPU load does not necessarily mean that there is something actually calculated there. It can also mean that the process is busy waiting at getting for data from - let's say - the secure enclave...

It is clearly related to the new hardware. The problem appeared on my business and my personal MBP only after updating to the new hardware with the T1 chip, on the old MPB there was no such lag despite using the same MacOS version and the very same iCloud keychain.

Strange is that is seems not to affect everybody. I can not imagine that this issue was still unsolved if some of the management staff at apple was also affected.

This is just a guess. I think if it affected everybody we would see threads about this problem on different apple fan sites like 9to5mac, appleInsider, iMore etc. I haven't seen any complaints there so far. It really makes the machine almost unusable at least for every web developer or you have to switch your development environment to another browser than Safari. I would expect people to shout louder.

I might be wrong of course, but I provided debug dumps to them it appeared to me that Apple is somehow not able to produce the problem in their labs.

I'm not so sure it's limited - having deleted all items in my keychain and gotten a replacement MacBook Pro iit's getting slower again as I remember more passwords.

Maybe it comes down to a particular website we all use or something stupid like that

I just visited an Apple store and tried out the issue on their demo MacBooks while having one of their guys with me. Any laptop with touch bar showed visible lag when accessing any item in the keychain (again, Demo accounts, not a lot of stuff in there but a visible beachball whenever trying to display the contents of an item in keychain). Any laptop without touch bar didn't.

I may be going on the wrong path (or not?) here but there are a number of new services and processes that I only saw on the touch bar versions such as com.apple.biometrickitd. I don't believe apple is oblivious to this issue since it's so easily to reproduce but a note that a fix is coming would be really nice.

Cheers,

Wow! If it really is hardware related (it was my first assumption that this is some kind of round-trip problem to the secure enclave) the new MBP with touch bar can be considered a failure. Since I'm having the MBP attached to an external screen I'm not using the touch bar really that often, however I found it a neat feature anyway. Maybe I can replace the MBP to a version without the touch bar? It is really nuts Apple released the product with this flaw!

At this point it definitely seems like an issue scoping ALL MacBook Pros with Touch bar. As someone who's had this for a bit over 2 months now - it's infuriating to see the low level of work I get done on this PC (piece of crap) because of this bug.

It's also a bit annoying how my apple case rep still calls to ask for screenshots and system reports...like **** isn't the whole apple engineering department using these computers professionally and personally by now??

Also upsetting how I just updated to the latest apple Beta while writing this post (10.12.5), and of course the issue is still there. This has got to be the worst and poorly handled bug I've ever seen in all my 12 years of Mac.

guys, do you have temperature ?

"The latest update (10.12.5) seems to fix this. Finally!"

"its slightly better but still an issue...."

NOTHING CHANGED, NOTHING

Probably it will be only one solution, introduced on WWDC.

Name of this fix: New MacBook 2017.....

Very Apple style.

I experienced the same issue with my 13" touch bar macbook pro. Contacted Apple (customer service in The Netherlands and pointed to this thread) and they asked my to go to an Authorized Service Provider. The Service Provider did some tests (new user with empty keychain -> no issues, new user with iCloud keychain -> issues, same iCloud keychain on fresh Macbook Air -> No issues).

Their conclusion was that it might be an hardware issue related to the Secure Enclave, but that they were not certain. I decided to go for a refund as I was within my two weeks refund period. I'll wait until a solution comes up in this thread, or for the (possible) announcement of the updated Macbook Pro at WWDC.

Everybody who has this problem should file a bug to apple. This is the only to raise the importance of the issue:

1) Got to https://bugreport.apple.com/

2) Open a new bug

3) Explain the problem. Make sure you mention that this happens on a new MacBook Pro with Touch Bar when iCloud Keychain is enabled and that prior to migrating to the new MBP you did not have the problem.

Thanks!

quick update,

macos 10.12.6 beta partly fixed safari, auto-fill now works fast, seems its precaching results in advance, though if you open "Other passwords" which is keychain itself - nothing changed.

I don't have any Microsoft_Intermediate_Certificates in my keychain despite the fact that I have MS office installed. So, it can't be this. My keychain tool is dead slow. When I type something in he search box after each letter I get the spinning ball for several seconds. I can't even type a word at once as I loose letters on the way.

Unusable. Still incredible disappointed about apple hat they don't address this.

I returned my 2016 13" 2,9Ghz TB MBp a few weeks ago, just got the new 2017 13" 3,1Ghz TB MBp and the issue is still there. So upgrading to latest model does definitely not solve this problem.

I'll test it this weekend with a fresh iCloud keychain and try to figure out if it's a certain certificate that causes this issue.

m.fromn,

How did you return it? That's what I need to do with mine. Were you just within the return period?

Unbelievable - that's ridiculous. Can't believe it's also in the new MBP. My only thought would be if High Sierra solves this?