Skip to content

Loading…

[Firefox] memory leak: zombie compartments and ghost windows #1046

Closed
The-Feminist-Software-Foundation opened this Issue · 5 comments

2 participants

@The-Feminist-Software-Foundation

uBlock 0.9.11, Firefox 36.0.1, Linux x64.

As titled, there seems to be quite some leaks happening with the versions mentioned. Compartments are zombified in the hundreds after a while of browsing.

about:memory returns a repeating pattern, under js-main-runtime-compartments and then user:

[Expanded Principal], ublock:sb:$SOME_NUMBER[$SOME_URL | ] (from: chrome://ublock/content/frameModule.js:195)

It's always (from: chrome://ublock/content/frameModule.js:195).

@chrisaljoudi chrisaljoudi changed the title from Memory leak: Zombie compartments and ghost windows in Firefox to [Firefox] memory leak: zombie compartments and ghost windows
@Deathamns

I can't confirm. The compartments are gone after a while, or if I hit "Minimize memory usage" in about:memory.
On what pages have you tried, have you disabled/enabled the extension in the meantime?

@The-Feminist-Software-Foundation

Mine stay even after minimising.

Pages tried in the session was an embarrassing mixture of 8chan, Reddit, eBay, Google, and Wikipedia.

I've disabled the extension in the meantime and fired up my old Privoxy adblocking solution.

@Deathamns

I tested these sites, and everything seemed okay to me.
You'll see at least the amount of compartments as many tabs you have opened, more if the tabs have frames in them. Which is also okay.
Not okay would be, if those compartments stayed in the memory after you closed the tabs.

@The-Feminist-Software-Foundation

Sorry to have wasted your time. The leak originated elsewhere and was only magnified by uBlock. Closing bug now and on with the leak hunting...

@The-Feminist-Software-Foundation

The leak seems to be caused by Greasemonkey in conjunction with the Youtube Link Title script. Sorry about the mis-reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.