I've been working on an Angular SPA app and I think I have discovered that having the 1Password extension enabled causes DOM nodes to accumulate and not be removed, and secondarily causes memory to increase without release. It happens when navigating to a page with a form, touching a text-input field on the form, and navigating away from that page. It doesn't happen if I simply navigate back and forth between the pages without touching the form's text-input field. When I disable the 1Password extension, the DOM nodes, JS heap, and listeners are all periodically reduced to minimal amounts.
I reported it on the Angular issues forums here: https://github.com/angular/angular/issues/36590, thinking it was an Angular bug initially, but am less sure now that it is. That post includes more detailed description as well as three screen snippets of the DOM node accrual from a performance recording in Chrome.
I'm a long-standing user of 1Password and am a huge fan of both the app and the browser extensions, so I'm hoping you might be able to shed some insight and maybe even offer a remedy or a workaround, or even point out to me something that I may doing wrong or misunderstanding.
1Password Version: 7.4.3
Extension Version: 126.96.36.199
OS Version: macOS 10.15.4
Sync Type: WLAN server
Referrer: forum-search:dom nodes