Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Severe slowdown in Chrome with 1Password extension 8.11.12.27 on pages with many inputs
Since updating to 1Password extension 8.11.12.27 in Chrome, pages with forms containing thousands of inputs freeze on load. The problem also occurs with many hidden inputs, which should not be processed by the extension.
We run an application that makes heavy use of hidden inputs. With earlier versions of the extension this was not a problem.
Profiling shows high CPU use in openOrClosedShadowRoot(), especially when called on the form element containing many inputs. After load, the function runs instantly, so the slowdown is tied to the extension’s initial DOM scan.
Steps to Reproduce:
- Install 1Password extension v8.11.12.27 in Chrome.
- Open a form with thousands of inputs, including hidden ones. Example: https://inputs-1password.netlify.app/
- On load, clicking buttons or opening the context menu is impossible.
- Chrome stays frozen until the extension finishes scanning.
Expected Result:
Pages should load normally, regardless of number or type of inputs.
Actual Result:
Pages freeze during load due to heavy time spent in openOrClosedShadowRoot().
Impact:
- Severe slowdown in apps with large forms.
- Users blocked from working with affected pages.
- Disabling Autofill options does not help.
- Using "Hide on this page" does not help.
- Adding data-1p-ignore to every input is not feasible for us.
- Rolling back the extension is not practical.
Workarounds:
None viable for production.
Proposed fixes:
- Optimize DOM traversal or revert to the previous methods.
- Support a parent-level attribute to exclude all children from scanning.
- Ensure that when the extension is disabled for a page, it truly does not inject or process elements on that page.
Hi everyone,
This should be resolved now in the 1Password browser extension as of 8.11.18. Please update and let us know how it's working for you!
10 Replies
- 1P_SimonH
Community Manager
Hi everyone,
This should be resolved now in the 1Password browser extension as of 8.11.18. Please update and let us know how it's working for you!
- 1P_Dave
Moderator
Hello avemarcus, notromda, oskarpearson, ceseshi! 👋
I'm sorry that you're seeing performance issue when using 1Password in Chrome. Our team is currently working on a fix for certain performance issues that have been reported to us. We're currently testing the fix in the nightly version of 1Password for Chrome (8.11.18.12 or later).
Would you be able to have your affected users test the nightly to confirm that it fixes the issue: 1Password Nightly - Password Manager - Chrome Web Store
If it doesn't help then let me know and I can help further.
-Dave
Issue=FS-3827
Hi Dave, I have tested the latest Beta 8.11.18.30 and it also seems to fix the problem. I will wait for the Stable to be updated to test it and notify my users.
Thanks!- 1P_Timothy
Hi ceseshi, thanks for testing that. I'm glad to hear the fix in the nightly has got things working as expected. Let us know if you see any issues.
Hey Dave! Thanks for the response. I tried the current nightly version (8.11.18.21) and it seems to have fixed the issue for me.
- 1P_Timothy
Thanks for giving the nightly a try! I'm glad to hear that fixed the issue. Let us know if you run into any issues.
We're experiencing something similar on a customized WordPress install, perhaps because its Customizer panel has ~1200 inputs hidden in it. Clicking into any input has a 1-2 second delay with the Chrome extension installed and "Offer to save and fill logins and other items" enabled.
DevTools is also reporting "focusin" handler messages from injected.js, similar to what notromda has mentioned.
This wasn't a problem for us before this week.
1Password for Mac: 8.11.14 (81114027)
1Password for Chrome: 8.11.14.24
Chrome: 141.0.7390.108I'm seeing a severe lag, on a form ... oh there it is, it too has a large number of options in several select boxes.
chrome developer console has messages like:
[Violation] 'focusin' handler took 14842ms injected.js:3
[Violation] 'focusin' handler took 15493ms injected.js:3
[Violation] 'focusin' handler took 14781ms
To be fair, that motivated me to re-code the form to use autocomplete and dynamic search to populate the form. much better for everyone!
Worth noting that we've encountered a similar problem with the recent release of the browser extension (v8.11.12.27, chrome 141.0.7390.55), but it's not related to many 'input' fields.
In our case it appears to be related to a page with a 'select' that has many 'option' values. On the page we have only 82 inputs and 26 selects, but we have over 23,000 options (!)
(We're going to change the approach here, but in the meantime it means we have to uninstall the 1password extension)
