Closed Bug 1350023 Opened 4 years ago Closed 4 years ago

High memory usage in Firefox 52 with uBlock Origin and Flashblock


(Firefox :: Untriaged, defect)

Not set



Tracking Status
firefox52 --- wontfix
firefox53 --- ?


(Reporter: mccr8, Unassigned)


(Keywords: memory-leak, regression, Whiteboard: [MemShrink])


(2 files)

(In reply to Howie from comment #98)
> This is absolutely an issue with FF 51 & 52 and isn't related to certain
> Add-ons (at least for me). I have both Flashblock and uBlock Origin
> installed and when I "downgraded" back to FF 50.0.2, the memory leak
> disappeared. With FF 51 and 52 I would rapidly (<10 minutes) see memory
> usage rise into the 1.4-1.6 GB range causing general sluggishness and an
> agonizingly slow user experience. I've been running 50.0.2 for several hours
> and memory usage is stable in the 620 MB range. I've deselected automatic
> updates until such time that this debilitating bug is corrected.
Can you please attach an about:memory report from when you are seeing high memory usage? We will not be able to investigate further without this basic information.
Flags: needinfo?(mhowie22)
Keywords: mlk, regression
Whiteboard: [MemShrink]
I  believe i might be seeing this in firefox 55 nightly, but it is not affecting content processes, only the parent process

Other Measurements

4,095.94 MB (100.0%) -- address-space
├──2,273.57 MB (55.51%) ── free(segments=530)
├──1,388.22 MB (33.89%) -- commit
│  ├──1,034.27 MB (25.25%) -- private
│  │  ├──1,028.07 MB (25.10%) ── readwrite(segments=2168) << pretty high for a browser not really doing anything)

This is occurring in a profile which has tabs open but unloaded, with only about:memory and about:performance opened.

Adblock Plus	true	{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Add-on Compatibility Reporter	2.2.3	true
Auto Unload Tab	true	{d3c46ca0-999d-11da-a72b-0800200c9a66}
Classic Theme Restorer	1.6.5beta1	true	ClassicThemeRestorer@ArisT2Noia4dev
Element Hiding Helper for Adblock Plus	true
Flash Control	2.1.4	true	jid1-sNL73VCI4UB0Fw@jetpack
h264ify	1.0.5	true	jid1-TSgSxBhncsPBWQ@jetpack
MEGA	3.8.12	true
Nightly Tester Tools	3.9	true	{8620c15f-30dc-4dba-a131-7c5d20cf4a29}
Open Link in Silent Tab	true	{d4c46ca0-999d-11da-a72b-0800200c9a66}
Restartless Restart	9.1-signed.1-signed	true
Search By Image (by Google)	1.1.4	true	{ce7e73df-6a44-4028-8079-5927a588c948}
Search Site	7.0	true	searchsite@DW-dev
Tab Mix Plus	true	{dc572301-7619-498c-a57d-39143191b318}
YouTube High Definition	52.0	true	{7b1bf0b6-a1b9-42b0-b75d-252036438bdc}
Anti Tumblr Infinite Scroll	1.2.1-signed.1-signed	false
DivX Plus Web Player HTML5 <video>	false	{23fcfd51-4958-4f00-80a3-ae97e717ed8b}
Hola Better Internet	1.41.290	false	jid1-4P0kohSJxU1qGg@jetpack

I have duplicated the profile into another instance of firefox and disabled adblock plus to test whether its related to auto filter updates,  but having tried doing them manually, they memory would release when forcing GC/CC and memory free from about:memory.
Well, it appears there is a memory leak in the parent process, and it has no visible cause.

i opened up a completely new profile and let it sit on about:memory and about:performance and got the same rate of readwrite increase as the profile with addons.
Is the data posted in comment 2 to comment 5 actionable?
Flags: needinfo?(continuation)
if not, i'll make at new bug.

i just caught about:performance consuming a core and causing firefox.exe to spike to 2.1GB in the clean profile, so something is up there.
Yes, please file a new bug. The original bug report doesn't have much detail so it is hard to know if it is the same as your issue or not.GraphWalker
Flags: needinfo?(continuation)
(Ignore the "GraphWalker", I just accidentally pasted that into my comment.)
This isn't actionable without any more information.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(mhowie22)
You need to log in before you can comment on or make changes to this bug.