1721122 - Uncontrollable memory usage grow

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, enhancement)

Description

[RostyslavL]

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

Steps to reproduce:

Steps to reproduce:

We've made a test app to reproduce a memory leak problem during loading/removing iframes 'n' - count abot 30 iframes into a table where each iframe is a representation of column with 'url' data in it.
There is a large jump in memory and energy consumption in case loading / removing of each iframe in 'about: performance' observator.
Also a high memory consumption level when deleting an iframe in 'about: memory'

iframe creation example :

    const createIframe = (url, name) =>{
        iframe = document.createElement('iframe')
        iframe.name = name
        iframe.src = url
        iframe.width = '100%'
        iframe.height = '100%'
        document.querySelector('td').appendChild(iframe)                     
    }

We need to know and understand if it is normal that after a long time of FireFox usage with 'Iframes' (about 30) in one app it takes up so much memory that 'setInterval' stops working and memory usage increases up to 7Gb RAM ?
Is there a bug or wrong method usage ?
How could this be avoided ?
Is there any kind of solution to resolve such kind of problem ?

Cause on other browsers this case is less affected

Actual results:

As a result the memory grows and grows overtime which results in degraded performance.

Expected results:

loading or removing iframe from DOM without giant uncontrollable memory usage grow

Comment 1

[RostyslavL]

The same mechanism does not occur on Chrome or Edge.
For FireFox version 68 there was a disconnection with usage about 2GB and FireFox version disconnection with usage about 89.0 7gb.
Edge after a long time consumes from 3.5 GB to 4GB and remains at this level without disconnecting instaed of Chrome Last version has not to be confirmed yet .
Screens with memory usage are below.

Comment 2

[RostyslavL]

Attachment: Edge last version memory usgage with iframes ganarated in application

Comment 3

[RostyslavL]

Attachment: chrome last version memory usgage with iframes ganarated in application

Comment 4

[RostyslavL]

Attachment: firefox v89.0. memory usgage with iframes ganarated in application

Comment 5

[RostyslavL]

Attachment: Attached image about:memory performance — Details

Comment 6

[RostyslavL]

Attachment: Attached image aboutPerformance.jpg — Details

Comment 7

[Andre Klapper]

Please enter the address
about:memory?verbose
in the address bar and attach (using the "Attach New File" link above) the output here.

Comment 8

[Andrei Purice]

Hey rotsy,
Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Also a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

Comment 9

[RostyslavL]

Attachment: memory-reportverbos.json

Adding about:memory verbose

Comment 10

[RostyslavL]

(In reply to Andre Klapper from comment #7)

Please enter the address
about:memory?verbose
in the address bar and attach (using the "Attach New File" link above) the output here.

I'd added what You asked for

Comment 11

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

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 12

[Emilio Cobos Álvarez (:emilio)]

(In reply to RostyslavL from comment #0)

Do you have a page where we could reproduce this? This is obviously not expected (unless you're keeping the iframe's window alive with JS somehow, like storing it in a global or what not).

Comment 13

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

Redirect a needinfo that is pending on an inactive user to the triage owner.
:edgar, since the bug doesn't have a severity set, could you please set the severity or close the bug?

For more information, please visit auto_nag documentation.