1592169 - High heap unclassified memory usage with OpenSpeedTest

Status: RESOLVED WORKSFORME

(Core :: DOM: File, defect, P2)

Description

[ENIGMA]

Attachment: Captura de pantalla (234).png

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Go to http://openspeedtest.com/ and do the speed test

Actual results:

While the test was successful, RAM usage of it's tab went to 2GB+ while the test was being made (returns to normal or almost normal after it ends), on lower spec machines, that can cause a lockup.

Expected results:

Not using 2GB of memory (even temporary) for the test.

Tried on Chromium Edge browser and Chrome, doesn't happen there, it stays at ~160MB

Comment 1

[Andrew McCreight [:mccr8]]

I took a memory report while this was running, and I ended up with a content process with 2.1GB of heap-unclassified. There was also around 100MB of memory-file-data/large/file. I'm going to guess this is DOM storage related, but somebody should put together a DMD build to be sure. I wonder if it is related to the string blob issue I was looking at earlier.

Comment 2

[Andrew McCreight [:mccr8]]

I also noticed that my heap-unclassified was really high in the parent process, and it didn't go away when I closed the speed test page, but I had that browser session open for a long time, so it might have been unrelated.

Comment 3

[Jens Stutte [:jstutte]]

I made a test with Nightly 96 and took a profile. Memory peak usage of the openspeedtest tab is 425MB. CPU usage is very high and most of it seems to be graphics related for painting the updates. But it all turns normal once the test finishes.

I think it is (was) unrelated to the Deezer issue, too. I'll close this WORKSFORME but feel free to re-open if you still see this.

Comment 4

[Mason]

I don't think users care about FF70, FF71, and FF68ESR at this point?