Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
cofiem
5 months agoNew Contributor
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...
- 4 months ago
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
5 months agoHello 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
DoctorBrown
5 months agoOccasional Contributor
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.