Skip to content

Chrome Extension Memory Leak #14002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
Sebastianmueller22 opened this issue Mar 26, 2025 · 7 comments
Open
1 task done

Chrome Extension Memory Leak #14002

Sebastianmueller22 opened this issue Mar 26, 2025 · 7 comments
Labels
browser Browser Extension bug

Comments

@Sebastianmueller22
Copy link

Steps To Reproduce

Not sure on that part. I am building a Vaadin Application, on which a user reported a memory leak (tab over 11GB RAM).
Your extension fires alot of "idle callbacks".
Upon analysing the memory of my app with the Chrome test build and browser internal memory heap snapshot, I could observe that there were hundreds of password fields and their respective CSS held in memory.

When the extension is enabled, my app has the memory issue.

When it is disabled, it does not.

My app makes frequent DOM manipulations and has a large DOM. Its basically a continuous queue of events that pop out of view once too large. Maybe that is what triggers your extension to fire? Could be related to this bug: #13558.

I know thats not alot to go with, I am down to provide more details though. I have heap snapshots and trace data from Chrome with the idle callbacks. I am not able to attach them here unfortunately (maybe they are too large).

Expected Result

No references to Password fields kept alive

Actual Result

Huge memory footprint, terrible performance

Screenshots or Videos

Image

Image

Additional Context

No response

Operating System

Windows

Operating System Version

10

Web Browser

Chrome

Browser Version

Latest stable

Environment Versions

2025.3.0

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@Sebastianmueller22 Sebastianmueller22 added browser Browser Extension bug labels Mar 26, 2025
@S-Kakar
Copy link

S-Kakar commented Mar 26, 2025

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-19529

@ValueXu
Copy link

ValueXu commented Apr 5, 2025

Thank you for reporting this issue! We've added this to our internal tracking system. ID: PM-19529

Me too! In Chome heap memory analyizer, it shows this extension created 260000 system / Context.

Image

I just watched the video on https://www.bilibili.com/video/BV1TB4y1f732, then I leaved my computer for a week (meanwhile I just used remote desktop and did nothing to the website which has leak problem). When I come back, I found this website has token 5G memory !

And this screenshot shows these system/Context may belong to these codes, hope this can help you solve the problem.

Image

@djarbz
Copy link

djarbz commented Apr 23, 2025

Sounds like my issue with Code Server, although I am only experiencing it in Edge.
coder/code-server#7320

@alexdc-info
Copy link

alexdc-info commented May 5, 2025

I'm using Edge, and I started running into this issue last week, memory usage was growing from the normal 100-200 MB to greater than 40 GB before it crashed (I have 64 GB of RAM). After reading the thread linked above, the only change I made was to disable the Bitwarden extension. I have not had the issue since. I've mentioned this in the other thread as well, but it does seem to potentially be Bitwarden on Edge causing the issue.

@archef2000
Copy link

I also have the code-server crash on Firefox and Chrome with the BitWarden extension.

@m0ta-ru
Copy link

m0ta-ru commented May 15, 2025

@archef2000 I confirm the problem

@DaveyUS
Copy link

DaveyUS commented May 17, 2025

Still a problem. Thought the webapp im developing had stuttering and it turned out to be bitwarden causing hiccups. It's coming from bootstrap-autofill-overlay.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug
Projects
None yet
Development

No branches or pull requests

8 participants