Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
1Password Firefox extension used to work fine, now does nothing
For approximately a week (about the last update), the 1Password Firefox extension does nothing. No prompts to fill username or password, and clicking on the 1Password icon in the browser bar seems t...
Hello folks,
Our developers have fixed an issue where the 1Password browser extension could become unresponsive in Firefox and cause abnormally high CPU usage. Please update to the latest version (8.11.4.27):
Thank you for your patience as we worked to develop and release a fix. If you're still seeing issues after updating then please send an email to support@1Password.com so that our team can investigate further.-Dave
1P_Dave
Moderator
ModeratorHello cofiem, DuchVeliky, grimbuehler, GaryH, DoctorBrown, Calion, and egerlach! 👋
I'm sorry that you're running into issues with 1Password in Firefox. I haven't yet been able to reproduce the issue on my end and I'd like to gather some more information. Can you reply to this post with the following information so that I can try to reproduce your environment:
- What version of 1Password are you using?
- What version of Firefox are you using?
- Are you using a Mac, Windows PC, or Linux device?
- In Firefox, while the issue is happening, open the task manager by navigating to about:processes, what do you see for CPU usage for Extensions?
- Are other extensions also unresponsive? Or just 1Password?
I look forward to hearing from you.
-Dave
I can no longer reproduce this issue.
- 1P_Timothy
Community Manager
Thanks for confirming that!
Hi Dave, thanks for combining my post with this one.
it is not clear what is triggering the issue. All I know is that sometimes in the middle of doing random actions in the browser I go to a webpage to logon to a site and try to invoke the 1P extension and nothing happens. I check Firefox Task Mgr and Extensions have floored the CPU usage. I kill the task and restart all the 1P extension and all is normal. This will also happen if 1P is the only extension enabled.
Have others seen this behavior?
It would help if I had some way to gather a trace of when this happens. Or gather other data to help.
What version of 1Password are you using?
8.11.0.29
What version of Firefox are you using?
140.0.4
Are you using a Mac, Windows PC, or Linux device?
Windows 11 Pro 24H2
In Firefox, while the issue is happening, open the task manager by navigating to about:processes, what do you see for CPU usage for Extensions?
CPU usage is 100% for extensions. See screenshots.
Are other extensions also unresponsive? Or just 1Password?
I only have 1 extension installed - 1Password.Consistent problem with others here.
- 1Password 8.11.0.29
- Firefox 141.0
- Windows 11 Pro
- CPU usage for extensions is pegged at 99-100%. I clicked the "Profile all threads of this process for 5 seconds" button and got the attached image, in case this is helpful to you to figure out where in the program it's getting stuck.
- Other extensions are also unresponsive.
I haven't managed to get the 1Password extension working by restarting (Firefox or computer), but I can get other extensions working by disabling the 1Password extension.
Hi 1P_Dave, I downgraded to 8.10.82.29 yesterday and that worked for me. I was trying to reproduce in a new profile, and noticed I couldn't, then re-upgraded to 8.11.0.29, and it seems to be working again now. I'll let you know if it fails again.
I had exactly the same symptoms as DuchVeliky shows in their video.
Hello,
after today update i have firefox version 141.0 and 1Password version 8.11.2. You can check my video with the problem:
https://www.youtube.com/watch?v=O-iHxfRCE_QSometimes it helps if I deactivate the add-on and reactivate it, but the problem returns very quickly. Uninstalling and reinstalling did not help. It seems that at the moment of the problem no add-on is working and not just 1Password, but I don't know if 1Password is causing it. I also tried deactivating all add-ons and activating only 1Password, but the problem is still there.
