-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
Thank you for reporting this issue! We've added this to our internal tracking system. |
Me too! In Chome heap memory analyizer, it shows this extension created 260000 system / Context. 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. |
Sounds like my issue with Code Server, although I am only experiencing it in Edge. |
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. |
I also have the code-server crash on Firefox and Chrome with the BitWarden extension. |
@archef2000 I confirm the problem |
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 |
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
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
The text was updated successfully, but these errors were encountered: