1874342 - Rapid memory increase on a demo that continues after you stop the demo, and profile shows 8s hang in content process and 1s in parent process

Status: RESOLVED DUPLICATE of bug 1883290

(Core :: Performance: Memory, defect)

Description

[Mayank Bansal]

First, the profile : https://share.firefox.dev/3NZaNJK
Second, disclaimer: This demo used to work fine but now it has this poor behaviour on both Firefox and Chrome. So something changed for the worse in the demo.
Third, reason for filing bug : Firefox is very much more impacted in terms of memory increase that doesnt stop increasing even after you stop the demo. Also, the profiler suggests 8s spent on the content process and 1s in parent process

Now, the STR:

1. Go to https://www.fxhash.xyz/generative/slug/littlecube-maps:-tropical-oasis-islands

2. Click on Run (Dont click on Open)
   --- > immediately, the content process will rapidly start using more and more RAM until it OOMs

3. Click on the Stop button (but keep the demo tab in foreground/in focus)
   -----> Memory keeps on increasing

4. The only way to stop memory increase is to Stop the demo and then put the offending tab in background. Then the memory will slowly crawl back to normal.

The profile suggests 8s of hang on the content process, and the parent thread also appears to be very busy.

In Chrome, the memory increase is slower and the response to stopping the demo is much more rapid.

Comment 1

[Mayank Bansal]

Not really sure whats the component. Adding few folks who will know better.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

This bug was moved into the Performance component.

:mayankleoboy1, could you make sure the following information is on this bug?

• ✅ For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 3

[Mayank Bansal]

Attachment: about:support

Comment 4

[Markus Stange [:mstange]]

I think the main reason for the memory usage is because the page is hitting so many JS errors, and we create runnables to log Uncaught TypeError: can't access property "y" of undefined to the console. Also, I think the page dispatches so many postMessages to itself that these messages continue to be processed after the stop button has been pressed.

Comment 5

[Markus Stange [:mstange]]

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: [x] Windows [x] macOS [x] Linux [x] Android
Websites affected: Rare
Resource impact: Some
[x] Able to reproduce locally

Comment 6

[Mayank Bansal]

This is probably a dupe of bug 1883290