1764227 - Out of Memory issue for ensonhaber.com

Status: NEW

(Core :: Performance, defect, P2)

Description

[Karl Dubost💡 :karlcow]

Steps to reproduce

1. Go to https://www.ensonhaber.com/
2. Wait a bit

Expected:
Site loading

Actual:
For some users the site is crashing the browser.

A performance profile.
https://share.firefox.dev/3IONjlG
https://github.com/webcompat/web-bugs/issues/100455
https://crash-stats.mozilla.org/report/index/5d90800a-fe28-4785-833e-dd8b60220302

See Also Bug 1405521

Comment 1

[Andrew McCreight [:mccr8]]

A memory report from about:memory would probably be the most useful thing, though maybe somebody can get something useful about what it is doing from the profile. The trick is that you'll have to get the report before the memory usage gets too bad but after it is bad enough. I tried leaving the page open for a few minutes on my computer, but I didn't see any particular memory issue. There was about as much image memory as there was for the entire rest of the web page, so perhaps there's some system-specific graphics issue people are hitting.

Comment 2

[Andrew McCreight [:mccr8]]

Can you reproduce this? Can you please attach a memory report showing whatever the high memory usage is? I can analyze that.

Comment 3

[Markus Stange [:mstange]]

(In reply to Andrew McCreight [:mccr8] from comment #2)

Can you reproduce this? Can you please attach a memory report showing whatever the high memory usage is? I can analyze that.

Comment 4

[Raul Bucata]

Here is the memory report, using the latest build of Firefox Nightly, from about:memory. Devtools does not work on the page, as the page freezes and the option is N/A.

Also, a pop-up informing that the page slows down Nightly is present after a while, with the tab crashing eventually.

Tested with:

Browser / Version: Firefox Nightly 103.0a1 (2022-06-16) (64-bit)
Operating System: Windows 10 PRO x64

Comment 5

[Raul Bucata]

Attachment: memory-report.json.gz

Comment 6

[Markus Stange [:mstange]]

Hmm, I don't see a high-memory process in that dump. There's a webIsolated=https://ensonhaber.com^userContextId=5 process in there but it's only 47 MB. Maybe the process was so unresponsive that about:memory could not collect a dump from it.

Andrew, thoughts?

Comment 7

[Andrew McCreight [:mccr8]]

(In reply to Markus Stange [:mstange] from comment #6)

Hmm, I don't see a high-memory process in that dump. There's a webIsolated=https://ensonhaber.com^userContextId=5 process in there but it's only 47 MB. Maybe the process was so unresponsive that about:memory could not collect a dump from it.

Andrew, thoughts?

The page is showing up in about:memory, so it does look like it collected a report. Unless it was opened in multiple tabs or something, but the STR didn't talk about that.

Comment 8

[Markus Stange [:mstange]]

Raul, was there high memory usage when you captured the report? If not, can you try to get another report when the memory usage is higher?

Comment 9

[Frank Doty [:fdoty]]

The Performance Priority Calculator has determined this bug's performance priority to be P2.

Platforms: Windows
Impact on browser UI: Renders browser effectively unusable
Impact on site: Renders site effectively unusable
Configuration: Specific but common
[x] Causes severe resource usage
[x] Multiple reporters

Comment 10

[Raul Bucata]

Markus, the report was captured at the peak of the problem, when the browser eventually crashes. If that does not reflect in the report or does not seem to capture the highest memory usage, I'll be more than happy to capture a fresh report.

Comment 11

[Markus Stange [:mstange]]

Not sure what the next step is here. Andrew, did you find anything useful in the report at the time?

Comment 12

[Andrew McCreight [:mccr8]]

No