-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix memory leaks #139
Comments
about memory (live measurement).pdf Memory mesurement for 11.6.0. |
Here no visible memory leaks are observed. |
For a permanent and fundamental solution, we are moving to a nonpersistent background page. |
Fixed possible sources for memory leaks in language overrides codes. |
Is this still an issue? |
@gmarkley-VI Combined with recent updates to Firefox, we do not see major performance issues with the extension, but if you find any, please report it here. |
I had major memory issues with Container Tab Groups so that I had to disable it to not have a big chunk of the memory be spent on with just a few tabs. When I had less than 5 tabs open, about 10-20 percent of memory would still be used, and if the tab count would go 8+, the memory usage jumps to 35-50 %. Haven't still debugged what's the actual reason for memory leaking, but this is the situation. |
Describe the bug
There is a memory leak related to per-container overrides.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Operates as normal, causing no memory leaks.
Screenshots

Console outputs
If applicable, open
about:debugging
> This Firefox and select Inspect for this extension. Then copy and paste what is in the console (you can hide your private information, if any).Nothing interesting.
Firefox (please complete the following information):
Additional context
https://discourse.mozilla.org/t/container-tab-groups-memory-leak-with-user-agent-overrides-enabled/111524
The text was updated successfully, but these errors were encountered: