When I try to fill in the password here https://www.albertsons.com/account/re-sign-in.html this happens, and stays that way.
Also, afterwards, the toolbar button becomes non-responsive in terms of displaying the drop down menu, or has a lengthy delay
@bituser I would recommend to do the following with your browser extension:
I followed your instructions to the letter. I believe 2025.7.0 is broken. In addition to the initial problems I reported, in the process of getting things done, FX 141 crashed several times, I experienced context menu problems, and the Bitwarden toolbar button displayed no badges.
I switched profiles and manually imported the session, history, etc. and updated Bitwarden. All the problems returned.
I removed Bitwarden, reverted back to 2025.6.1, and things seem to be back to normal, including now being able to login on that website I originally mentioned.
One odd thing just happened. I logged into Bitwardwn, and did the 2-step verification. I tried to log into this website, using my email. Nothing happened. Rebooted.
After reboot, I was again logged out of BItwarden. I logged back in, did the 2-step, and this time logged in with my username instead, and here we are.
Using the original profile.
Ups, that sounds very unfortunate.
You probably don’t want to try it again, but if you do, you can report bugs on GitHub. - I just checked and no specific new reported “Firefox bugs” so far.
I just tested my own Firefox extension and I didn’t see any of the things you described (with extension 2025.7.0).
Please see my edited reply.
Hey, I’m not sure I understand your addition completely, so please clarify…
Are you implying, that your autofill problems you reported about 4 hours ago (and thought would be due to 2025.7.0) are now also occuring on extension version 2025.6.1?
That’s probably not surprising. As you followed my steps above you also resetted all settings of the extension. So you have to set up vault timeout action to lock etc. again – and I would guess, then the extension doesn’t log you out again with a reboot.
As I don’t know if you use your email or username for autofill for this site, I don’t completely know what you are trying to say here. But autofill then works again?
By that you mean the Firefox profile, you used the BW extension before on?
For what it’s worth, in a Chrome browser on a Windows 11 system, I have no issues autofilling on the above link. For you, does the problem only happen on the Albertsons login page, or on all web pages? What browser/operating system are you using?
Another thing you might try is to disable all browser extensions except for Bitwarden. A simple way to do this would be to enable Bitwarden’s browser extension to run in Incognito/Private mode, but do not allow any other extensions to run in Incognito/Private mode. If you now go to the Albertsons login page and open the Bitwarden extension, do you see the same behavior?
I think there now is a GitHub issue with similar reports (PS: And so far, it seems to be limited to Firefox.):
That’s a relief. I’ve had several instances in the past, one recently, of a corrupted Firefox sessionstore file that prompts weird behaviors, some symptoms similar to this.
After I posted, It dawned on me that because I uninstalled BW, I had to set 'Vault TImeout" to never. I was also gonna report that i have a ton of tabs (too many) that maybe contributed to the crashes if the root of the issue was already taxing the ram.
I’m guessing that the username thing is somehow related to the BW ram issue,
I can post over there if you think it’s necessary, but besides confirmation, I don’t know what I can add in the way of a technical contribution.
Thanks
There now is a hotfix update only for Firefox (2025.7.1) and it’s already available in the Mozilla store.
Blockquote
There now is a hotfix update only for Firefox (2025.7.1) and it’s already available in the Mozilla store.
is it working for you? Not me. Same problems.
Please go to Settings > About > About Bitwarden, click Copy, and paste the results in a response here.
Blockquote
Please go to Settings > About > About Bitwarden, click Copy, and paste the results in a response here.
Is it working for you?
I have to revert to v2025.6.1. For me, both updates that follow are not usable. Same symptoms.
I was not affected by it in the first place. (and don’t use Firefox that often nowadays)
A Bitwarden developer just posted this an hour ago:
So, 2025.7.1 should fix this particular problem, Browser crash due to huge memory usage when unlocking vault. Version 2025.7.0 · Issue #15899 · bitwarden/clients · GitHub stays open, and you should probably report there when your (corresponding) issues still persist.
Blockquote
So, 2025.7.1 should fix this particular problem, Browser crash due to huge memory usage when unlocking vault. Version 2025.7.0 · Issue #15899 · bitwarden/clients · GitHub stays open, and you should probably report there when your (corresponding) issues still persist.
I posted there, among a few others that reported still having the problems. From my experience, I believe it may be related to excessive tab sessions.
It’s been over three weeks. Since the problems, for at least some users, persist, and the github thread is no longer being responded to by the developers, are we to assume the issues will no longer be addressed, and the affected users have no choice but to seek out a Bitwarden alternative?
A post was split to a new topic: Firefox crashes
