Harry Bosch Reporter
	Description • 7 years ago

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170612122310

Steps to reproduce:

I was using Firefox for a few hours on my Ubuntu desktop 16.04 LST.


Actual results:

Firefox becomes slow, lags, unresponsive. Keyboard entry is delayed by seconds, when you hit a key it takes a while to appear. 

I now have a single tab open showing http://www.google.com.

I checked memory usage on my 4yo Linux box (Intel Quad 3.7Ghz, 16Gb RAM, SSDs) and found that 1.8Gb are being used by Firefox.


Expected results:

Firefox should clean up it's memory when tabs are closed etc. 

If you need any help with the diagnosis, I'll willingly collect data etc.

	Harry Bosch Reporter
	Comment 1 • 7 years ago

Closing Firefox and reopening. Memory usage 234 Mb.

	Harry Bosch Reporter
	Comment 2 • 7 years ago

Ubuntu 16.04 LTS, 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
p

	Abe - QA (:Abe_LV)
	Comment 3 • 7 years ago

Hi Harry,

Could you please provide a memory report?  Thanks

Steps to generate a memory report:
1. Navigate to the desired website and wait until memory usage is high
2. Open a new tab and type "about:memory" into the address bar and hit enter
3. Click on the "Measure and save..." button
4. Attach the file to this bug.

Detailed information is available here:  https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory

	Harry Bosch Reporter
	Comment 4 • 7 years ago

Memory allocation shown directly in O/S.

	Harry Bosch Reporter
	Comment 5 • 7 years ago

The allocation seems to show a number of windows. 

Note #1 ALL tabs/windows, except about:memory were closed when I took the memory shot.

Note #2 A lot of the memory allocations (malloc) seem to relate to youtube sites.

Note #3 I only have native html5 video activated: NO flash wtc.

Note #4 The issues appear to be threefold
-memory leakage #1 closed tabs/windows leaking
-memory leakage #2 relating to html5 resources
-memory leakage #3 relating to strings 
 
I'm going to GC and CC and then upload that too...

	Harry Bosch Reporter
	Comment 6 • 7 years ago

After submitting the first memory report, I "GC"'d and "CC"'d on the about:memory tab. 

This cleaned up 50% (ca 1.4GB) of the windows/tabs, youtube and string mallocs.

So I'm "guessing"... GC Garbage collection does not seem to be taking place.

The external MEMORY USAGE in UBUNTU is still showing 3.8 GB afterswards.

Be aware (GUESS): It may have to do with me running 64-bit Linux? Spawning external processes maybe?

Best wishes, Harry

	Abe - QA (:Abe_LV)
	Comment 7 • 7 years ago

Hi Eric,

Comment/suggestion on memory reports provided above?

Thanks

	Eric Rahm [:erahm]
	Comment 8 • 7 years ago

My guess is that some of your add-ons are keeping pages alive longer than they should. Can you try disabling them and seeing if things improve? If that helps you can start re-enabling one by one to figure out which one is causing your problems.

My main guesses are uBlock and NoScript.

	Harry Bosch Reporter
	Comment 9 • 7 years ago

Memory Report with uBlock, Noscript and Ghostery deactivated before I GC'd and CC'd

	Harry Bosch Reporter
	Comment 10 • 7 years ago

Memory Report with uBlock, Noscript and Ghostery deactivated after I GC'd and CC'd

	Harry Bosch Reporter
	Comment 11 • 7 years ago

I carried out Eric's recommendations. Memory usage now 2.5 GB with with uBlock, Noscript and Ghostery deactivated. All windows/tabs except about:memory were open. 

The heap consumes 723Mb (overhead) + 126Mb (unclassified). Network 40 Mb. 

Process Monitor (external to Firefox) still shows 2.5Gb usage.

	Eric Rahm [:erahm]
	Comment 12 • 7 years ago

(In reply to Harry Bosch from comment #11)
> I carried out Eric's recommendations. Memory usage now 2.5 GB with with
> uBlock, Noscript and Ghostery deactivated. All windows/tabs except
> about:memory were open. 
> 
> The heap consumes 723Mb (overhead) + 126Mb (unclassified). Network 40 Mb. 
> 
> Process Monitor (external to Firefox) still shows 2.5Gb usage.

The 2.5Gb number is probably virtual memory, we see that there's a high amount of decommitted (1.3Gb) which is memory we've told the OS it can have back. So overall this is much better. Can you try re-enabling your addons one at time to see which one was causing the youtube pages to stick around?

	Abe - QA (:Abe_LV)
	Comment 13 • 7 years ago

Hey Harry,

Could you provide memory report based on comments 12?

	Abe - QA (:Abe_LV)
	Comment 14 • 7 years ago

Closing this as incomplete due to inactivity and lack of response from the reporter.
If anyone can still reproduce it on latest versions, feel free to reopen the bug and provide more information. Thanks