A reboot seems to have fixed everything.

On email the discussion yielded "this is a failure to decrypt". A rogue app spun out of control and ate all my memory. I killed it, but it must have left the keychain broken.

Thanks for your help.

So Mac Keychain getting wedged makes Chrome behave poorly.

- Do we want to file a bug with Apple? System services should be reliant to rouge apps eating all the memory.
- Do we want to look into testing for Mac Keychain sanity in Chrome to guard against this?

e.g. With Chromium on Mac, if I deny the keychain access request, then components/os_crypt/keychain_password_mac.mm line 76

OSSTATUS_DLOG(ERROR, error) << "Keychain lookup failed";

prints out:

Keychain lookup failed: Error Domain=NSOSStatusErrorDomain Code=-128 "userCanceledErr" (-128)

I wonder what that would output when Keychain is in a bad state.

Can this be readily reproduced with a memory hog running alongside Chrome?

I haven't tried to repro it. My recollection is that the rogue app ran things so far out of memory that the "you have no memory" dialog appeared. In addition, this wasn't the only time this memory thing happened but this was the only time that the keychain issues happened.

Ran into this myself, seeing the "failure to decrypt" message in the logs. A computer restart sorted everything out. :)