Forum Discussion

miroljub1995's avatar
miroljub1995
New Contributor
9 months ago

Memory leak with Chrome extension

We noticed that we have memory leak when using 1password extension in Chrome. Here is a minimal repro code. <!doctype html> <html lang="en"> <body> <button id="btn">Test the click and wait fo...
browser extension
macos
1P_Dave's avatar
1P_Dave
Icon for Moderator rankModerator
8 months ago

Hello miroljub1995! 👋

Thank you for reporting this! I've done some testing and I'm not seeing the EasierToFindInShapshot being retained when I have 1Password in the browser enabled. Here are my reproduction steps: 

  1. Saved your code as a HTML file and opened the file in Chrome. 
  2. Opened the Memory tab in DevTools.
  3. Pressed the "Test the click and wait for removal" button. 
  4. Took a heap snapshot. 
  5. Waited for the button to disappear.
  6. Took a second heap snapshot. 


Whether 1Password in the browser is enabled or disabled, the second snapshot doesn't contain reference to EasierToFindInShapshot.

Here are the versions that I'm using: 

  • Chrome version 133.0.6943.127
  • 1Password in the browser version 8.10.62.27


Can you reproduce the issue using the same versions that I'm using? If you can then can you let me know if I got the reproduction steps wrong? 

-Dave