george Reporter
	Description • 7 years ago

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce:

For Google Docs (Gapps)

1. Open Google Drive
2. Open A document with some texts
3. The initial memory usage is very high (70-100MB for drive browsers, 100+MB for each document)
4. Let it sit. I have a google docs document that sat over night and is at 400MB

For Twitter: 

Open Twitter and let it sit. It will start at around 70MB and balloon to about 100-150 MB

For Azure Portal: 

Open azure portal it normally sits around 300-400MB memory usage

Additinally, I have attached an anonymized about:memory, I have available GC and CC logs, as well as a a Windows Memory Dump file available (I would prefer to pass these along privately as they could possibly have info I don't want public, and are very lart (~7GB)


Actual results:

After a while FF Memory usage goes up to between 5-7GB (x64 build) The interface gets slow and non-responsive. 


Expected results:

Memory usage should not leak, and should not be that high. Additionally the interface should not hang when under high memory usage.

	Cosmin Muntean [:cmuntean], Ecosystem QA
	Comment 1 • 7 years ago

Hi George,

Can you please attach the information from "about:support" page?

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

Hi george, from the memory report it looks like you have about 115 active tabs open, does that sound right? If so this memory usage isn't completely unexpected.

As far as increasing over time, again this isn't completely unexpected for a site like twitter that is constantly updated. For Google drive we have seen some memory related issues in the past, bug 1336811 recently fixed a leak and is available in Firefox beta (52) if you'd like to test that.

	george Reporter
	Comment 4 • 7 years ago

I believe at the time of that snapshot I only had about 20 or 30 tabs open. I'll close everything out and let the biggest offenders run over night and upload a new snapshot tomorrow. 

I'll also give 52 beta a try today and let you know.

	george Reporter
	Comment 5 • 7 years ago

I let FF 52 beta run over night, and while things are still using memory, it no longer appears to be leaking. Normally I'd be at about 4-7GB memory used at this point and the app would be laggy and un-responsive. On 52 beta it is still usable, and not laggy at all. 

My guess is that the google drive fix resolved issues with other web apps as well. 

I'll let things run over the weekend, and if 52 beta continues to behave better I'd call this resolved with 52. 

Let me know if there is any testing or diags I can run for you on the beta build.

	Cosmin Muntean [:cmuntean], Ecosystem QA
	Comment 6 • 7 years ago

Hi George,

Have you managed to reproduce this issue using Firefox Beta 52?

	george Reporter
	Comment 7 • 7 years ago

No repro in FF 52. Looks like it was fixed there. 

Thanks!

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

Great news! Thanks for working with us george. I'm going to close this for now, but please feel free to reopen if you see the issue again.