Hey @aswang don’t hesitate to share more detail with the support team at Help Center | Bitwarden
It seems the issue is mostly resolved, however there is a 1-2 second delay each time I click the plugin icon in the browser, before it shows the “main menu” or list of items.
for what is worth, i also have a 1-2s delay after clicking the browser extension.
when did it start? idk, but this has been going on for at least 2 months. no, reinstalling doesnt help.
Version: 2025.5.1
SDK: 'main (c6835e5)'
Server version: 2025.6.1
secondary rant: if bitwarden wants more info about how and where the app/extension is run, that should be included automatically when copying the information from the about modal
I can confirm this. Same happened to me in the same workflow.
Uninstalling and reinstalling the extension from the store fixed the issue.
1 Like
This continues to be a problem. Clearly when transitioning to React, something went wrong with the extension - perhaps the default JS bundle takes too long to load. I have a Macbook M1 Max with 64 gigs of RAM. The performance is atrocious, like I’m running on a Pentium II processor. Slack, of all programs, starts from a cold start faster than this.
Here are the details you’ll probably want
Version: 2025.7.0
SDK: 'main (f2bc708)'
Server version: 2025.7.2
If it helps, this message spams in the console
background.js:2 Error while processing message in RuntimeBackground 'triggerAutofillScriptInjection'. Error: Frame with ID 33060 was removed.
The ID changes, but every 10 seconds this is logged to console.
Did you already try to “reset” the extension? Like following this whole sequence:
- log out in the BW app (be sure you can log in again! → master password and 2FA or “new device email verification code” etc.)
- deinstall the app
- check if the local data of the app is deleted (Data Storage | Bitwarden)
- restart your computer
- re-install the BW app
- log in again
?
Sadly this has no effect. It remains slow. Is there a vault size limit or something causing this?
@Roshan_George For some people, this seems to fix it – and unfortunately not for others. I don’t know of any definite answer here. And you’re probably already familiar with the corresponding GitHub issue, where you can add your details at least.