Forum Discussion

ceseshi's avatar
ceseshi
New Member
5 days ago

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:

  1. Install 1Password extension v8.11.12.27 in Chrome.
  2. Open a form with thousands of inputs, including hidden ones. Example: https://inputs-1password.netlify.app/
  3. On load, clicking buttons or opening the context menu is impossible.
  4. 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.

1 Reply

  • 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)