You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
When the main frame is navigated, its frames are not cleared from tab store.
When a frame is removed, it is not reflected in the tab store.
The first problem is easy to fix, but it's not that important, maybe 1 kB here and there, no rush for that.
The second problem is more difficult to fix, it affects uBlock Origin (and Nano) as well.
The text was updated successfully, but these errors were encountered:
1 is fixed. I'm not sure how to deal with 2 though...
jspenguin2017
changed the title
Potential temporary memory leak when a webpage inserts and removes lots of frames
[Bug] Potential temporary memory leak when a webpage inserts and removes lots of frames
Jan 17, 2019
Related discussion:
- https://bugzilla.mozilla.org/show_bug.cgi?id=1652925
It's not clear the code here will fix the reported
issue, but I did identify that the subframe
dictionary of a very long-lived web page can
theoretically grow unbound.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The first problem is easy to fix, but it's not that important, maybe 1 kB here and there, no rush for that.
The second problem is more difficult to fix, it affects uBlock Origin (and Nano) as well.
The text was updated successfully, but these errors were encountered: