I’m using 2024.12.4.
I have two Chrome windows open, each with a different profile. One authenticated bitwarden extension, the other unauthenticated.
Unauthenticated version hangs when first clicking on it. Disabling and enabling the extension worked.
Now when authenticated there is still a 2-3 lag in opening the menu.
Chrome version: Version: 2024.12.3, running on Mac.
The first time I use the plugin after opening, it takes 30s or more to load.
The slowness started for me when the new UI was introduced… can we go back to the old UI that was responsive somehow until this is fixed?
@myrison Welcome to the forum!
You can sideload version 2024.11.2.
another report:
version 2024.12.3
chrome: Version 131.0.6778.205 (Official Build) (arm64)
1-ish second delay when authenticated
very long delay when not authenticated
Same issue. Slow and sluggish response from the app.
version 2024.12.4
Chrome: Version 131.0.6778.205
On mac chrome, autofill is slow when using Cmd + Shift + L. It’s significantly slower with the latest update of Bitwarden that included all the UI changes.
Sonoma 14.6 (23G80)
Chrome Version 131.0.6778.205 (Official Build) (arm64)
Bitwarden Version: 2024.12.4
@kitduncan Welcome to the forum!
Hm, do you see your “symptoms” in this thread: Chrome extension takes forever to load UI after authenticating and is extremely slow and unresponsive ?
(if yes, then you seem to experience this bug now as well - and it would fit in, as Chrome and mostly MacOS are affected…)
I don’t have those other symptoms but yes it’s Chrome. I tested on Firefox and it works great.
Hm, I think in that thread, the symptoms also vary… for some people, only a few small delays here and there - and for others 20-30 seconds until the extension window even opens.
I can neither assess nor “decide” if it really is the same bug, but if you see that difference between the Chrome and Firefox extension, I would tend to think that it is might be the same bug, but not affecting you that much as some others. 
Oh ok. I’ll wait to see if that bug is fixed and hopefully it’ll fix the issues I’m experiencing. Not sure if you’d rather remove this post and I’ll bookmark the thread you referred me to. Thanks!
I thought of a similar thing… As you see, for now I’ve move our conversation into this thread. 
Hello,
I have been facing this issue also on my machine Chrome OSX arm64 bitwarden version 2024.12.4
Colleague recently complained also…however two other colleagues have no issues, it seems very random…
Hi everyone, this is a known bug affecting some community members. Will be fixed in an an upcoming Chrome update. In the meantime, you can try Canary to resolve the issue.
Any idea when that update will be available for general release?
Such a basic function is broken for over a month and a decision was made to not revert?
Now Bitwarden is down for an hour (confirmed by downdetector) and status page still says “Operating Normally” with increased latency? Can’t tell the difference between HTTP 5xx and slow? the worst of all the UI doesn’t even warn user save failed so data got lost permanently. Then users actually got locked out of vault as offline access is broken as well
Bitwarden has really gone downhill and users should seriously consider migrating to something that treat users like s***
They are currently in the midst of an advertised outage, as reported on the top of this and every community page:
The chrome slowness is reportedly an issue with the Chrome web browser and it is Google who will be releasing the update. “Canary” is the name for Chrome beta/nightly updates.
maintenance did not say this is service impacting. 3 hours downtime for a password manager is a joke… It is a botched maintenance, just like the botched December release, with Bitwarden keeps gaslighting users every time an issue gets reported. It took almost 2 hours for the status page to show degraded service speaks the level of competence at Bitwarden
That maintenance has finished 30 minutes ago, and that’s when it all gone down the toilet… I’ve just came here because my Bitwarden refuses to let me into my vault… on all devices… on different networks… with 500 Internal Server Error response for the backend…
I had no notifications of any kind about this so called “planned outage” on any of the comms channels. If this is a planned outage, at least an email would be nice. Posting a message in a community form and assuming that’s fine just isn’t good enough guys.
I’ve been a paying Bitwarden customer for years, and I’m strongly considering alternatives at the moment…
They do have a RSS feed for their status page, which includes an entry for the planned outage and also one for the current service degradation.
My mail client is able to subscribe to RSS feeds. If yours does not, there are services which will monitor a RSS feed and send you an email when it changes.
Yeah, right…
Tell this to your mum or an “average Joe” user whose deepest expertise only includes the knowledge on how to install a mobile app and pay for a subscription.