kpiris
(Kiko Piris)
January 8, 2025, 2:06pm
102
I’m not affected by this (for now ).
Isn’t there any other option other than upgrading chrome to canary?
I wouldn’t consider upgrading to canary to be a reasonable solution for any non-technical user.
Chrome canary channel can be quite unstable, and for today’s canary to reach the stable channel, it could take more than 3 months.
I don’t think this is reasonable for something so critical as a browser.
I too am not impacted and keeping my fingers crossed.
I have seen reports that logging out and back in or reinstalling the extension (perhaps after removing the local storage ) helps some people.
If that does not do it, I’ll ride out the storm using Firefox, Edge, or Safari.
Today it took 17 seconds for the extension window to open in Chrome. Ridiculous.
@southerndoc I redirected your post to this thread, as it belongs to this bug here. (your post was before in the thread “Revert to older UI design” - but this bug also began with the old UI and seems to be connected to Chrome itself)
grb
January 9, 2025, 5:22pm
106
A user on the Github thread made an interesting observation:
opened 04:20AM - 08 Dec 24 UTC
bug
browser
### Steps To Reproduce
1. Start Chrome
2. Click on Bitwarden extension icon.…
### Expected Result
Vault should react instantly.
### Actual Result
Around 3 seconds (up to 10 seconds) until Bitwarden reacts, usually 3 seconds.
### Screenshots or Videos
https://github.com/user-attachments/assets/9c8f0f3d-5cd7-4779-b83b-18aac338a231
### Additional Context
_No response_
### Operating System
macOS
### Operating System Version
_No response_
### Web Browser
Chrome
### Browser Version
Version 131.0.6778.109 (Official Build) (arm64)
### Build Version
Version: 2024.11.2,
### Issue Tracking Info
- [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
1 Like
Hopefully this gets fixed soon. I can’t use Canary builds on my computers due to work requirements.
… there is some news from a Bitwarden developer from the GitHub issue (just posted there):
(here the direct link to that message: Bitwarden extension is very slow. · Issue #12286 · bitwarden/clients · GitHub )
4 Likes
Demerre
January 13, 2025, 7:46am
109
Unfortunately, it’s still not working properly for me after renaming that…
Just to forward it to here again (as I receive email notifications of that GitHub thread now ): there are two new reports now, that suggest, that removing Chrome and a fresh install of Chrome worked for them.
PS: And the last few people wrote there, that also other extensions on Chrome showed a similar slowness etc., indicating again, it very likely is a Chrome issue.
Another update from a Bitwarden developer:
3 Likes
Tornado
January 13, 2025, 6:11pm
112
This is the solution! Thanks!
1 Like
Povi
January 16, 2025, 1:16am
113
Previously logging in took a bit longer for me. Today I updated Chrome (132.0.6834.84), and I can feel a significant difference on both Windows and MacOS devices, Bitwarden opens immediately after clicking, with instant biometric login.
4 Likes
The first time I opened it was just as slow, but subsequent times seemed to improve.
Demerre
January 23, 2025, 6:41am
115
WIth the version Version 132.0.6834.84 (Official Build) (arm64) it seems it’s fixed now!