[rckoepke]

Instant wake for me. However any time I come across a password field in a website the computer freezes for a painfully long 10 seconds or so while it presumably decrypts my password vault.

Sometimes this will happen multiple times per page load if I deselect and reselect the password field.

[sephamorr]

Oh goodness I thought this was just me after searching online and finding very little, if any, discussion of the bug. The issue I had wasn't on password login prompts, but on account creation prompts (i.e. password+confirm password). I had assumed it was lastpass at first, but the freeze persisted even after removing that -- on a one-day old computer.

[astrange]

Feel free to report it in Feedback Assistant.

[sephamorr]

I gave up on reporting bugs to Apple a while ago. The experience, repeated several times over, of spending all the time to file a radar, gather all the logs and files that Apple insists on (probably reasonably), then submitting the thing and getting exactly zero feedback for the next year when you are then told to repeat all the same work on a new macos version or the radar will be automatically closed, is demoralizing. Mind you, the issues I reported were fixed/went away a few years after that (so clearly not as a result of the then-long-closed ticket), but the process just feels like a waste of time to interact with the black box of apple.

[astrange]

It helps more than nothing. I would recommend just becoming more casual about it.

My experience maintaining projects is actually not that people don't provide enough info in their bugs (certainly true for random forum rants though), but when they try they try too hard and end up spending a long time writing a bunch of stuff I don't even read, because the log speaks for itself.

In this case you're not necessarily reaching an engineer, it could go to someone who combines reports together, or the fix is because of your report but it doesn't get communicated back properly, but it's still letting someone know it's a problem.

[cpressland]

This happens to me too, I’m using 1Password. I have a suspicion the plug-in is involved with this but I’ve not had time to collect evidence yet. Seems to be rare though, I’ve not spotted anybody else with this issue.

[climb_stealth]

I am seeing lots of spinning balls with 1Password on my 2015 Macbook Pro. Even just switching between fields with the keyboard brings up a spinner for two seconds or so. It's a recent thing I think. No other app has any issues.

[hderms]

Is it possibly due to the x86 emulation? I could see something like that being the cause

[climb_stealth]

Apparently the latest version 7.8 runs natively on Apple Silicon.

[loeg]

I see the same thing on native x86 1Password.

[climb_stealth]

I just updated to version 7.8 from version 7.7 and it looks fine so far. I haven't seen any freezes in the five minutes that I have been using it.

This makes me realise how much of a pain it has been to use in the past weeks or so. Now that it is back to normal snappy it is such a pleasure to work with again.

[thefourthchime]

Huh, no problem here. I use lastpass and safari's built in password thing.

[other_herbert]

Anecdotal but keeper and the built in keychain are instant ish at least not slow enough to notice

[terramex]

I don't use any external password manager, only Keychain and Safari and I see this 10-15 second delay every time when adding new password to Keychain since day 1.

It is my only issue with M1.

[Waterluvian]

Did you somehow accumulate a bajillion passwords?

[CameronNemo]

Crypto optimizations are no joke. My Pinebook Pro takes several seconds longer than my T430 to decrypt my keepassxc database.

[akvadrako]

Maybe the time is hashing your password. This is designed to take as long as it can while still being reasonable. 1 second on a fast machine isn't unheard of.

[coldtea]

Why would it need to decrypt a whole database though, and not just the required password? To avoid leaking the key name?

[CameronNemo]

Yes I think it is an all or nothing deal.

[coldtea]

Perhaps it could be a two-level thing then, where you first decrypt e.g. the list of keys and then read the one you want and get a "start/end" offset to read/decrypt just the value for that key from another file. So keys and values are still decrypted, but you don't have to decrypt the whole bundle in one step to get the value.