1439280 - Massive memory leak in a content process

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Masa Péter]

Attachment: The screenshot

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180125163041

Steps to reproduce:

1. Open player.epidemicsound.com
2. Click browse
3. Filter for electronica & Dance (Optional, but i didn't checked without filtering or with other filters)
4. Start listening, and wait. Do what yo usually do, because it will need some time.
5. You noticed tracks are switching slowly? The player content process may also use cpu and gpu for some reason (checked, no mining scripts are running)
6. Check with a modern task manager (for example Process Hacker) how many ram + pagefile Firefox uses. You can see that in the "Private bytes" column in the screenshot, and also in the window next to it



Actual results:

A content process started to use heavy amounts of ram. It means Firefox filled up my pagefile to 27 GB (22 GB is used by Firefox), and until i reduced FF's working set with Process Hacker it used 5 GB ram (now 1,9 GB).

more info here: https://gist.github.com/MPeti1/e64727a76f7d469bc0456b5fd6a179fd
if you need it i can also provide a memory dump of the leaking content process, but only if you allow me to upload files of about 23 GB (it will be growing by the time)


Expected results:

garbage collection

Comment 1

[u554753]

Moving to General.

Comment 2

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Can you recreate this state and get a sample through about:memory and attach that? 

If not, if there's a place you can stash the memory dump and share the URL to it? 

We don't have a good way to process a large memory dump file, however. 

Thanks.

Comment 3

[Masa Péter]

Sorry, I wasn't able to reproduce it. If I encounter the problem again I'll make a memory dump.