1872356 - memory usage grows and tab crash or get inaccessible

Status: NEW

(Core :: JavaScript Engine, defect, P3)

Description

[Dieter Ferdinand]

Steps to reproduce:

i use the victron portal: https://vrm.victronenergy.com and open the dashboard or a site with diagrams.

Actual results:

after some hours, firefox use more then 4 GB ram for this tab and the tab seems dead. i must restart firefox or the tab crash.

this site refresh the data with javascript and use much memory over the time, if the tab is active.

Expected results:

the portal displays the actual and history data of a pv-system.

Comment 1

[Mayank Bansal]

Hi Dieter
https://vrm.victronenergy.com/ needs a login. Without logging in, we cant repro and hence it will be unfeasible to diagnose the issue. There are couple of things that can help:

1. Copy about:support into your browser, and paste its contents here
2. When you experience this issue, please generate a memory report with the guide from here: https://firefox-source-docs.mozilla.org/performance/memory/about_colon_memory.html , and share the geenrated report here
3. Create a Firefox profile using the guide here : https://profiler.firefox.com/ , and share the link here

If all these steps do not help to reproduce the issue, the last resort would be to share the login credentails privately to a Firefox dev so that they may try to reprodiuce it themselves. Note that most of the Firefox developers are away due to the holidays.

Comment 2

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

This bug was moved into the Performance component.

:dieter.ferdinand, 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

[Dieter Ferdinand]

hello,
here a share-link to the portal:
https://vrm.victronenergy.com/installation/364414/share/1b27618d

to get the other data, i must wait some time because i close the browser while it use more then 6 GB ram for two processes.

goodby

Comment 4

[Mayank Bansal]

I have not been able to reproduce the memory increase on the URL you have shared.

Comment 5

[Dieter Ferdinand]

Attachment: memory report

Comment 6

[Mayank Bansal]

memory report does show 2GB+ in a process, and it is all in non-gfx area.

It would be very helpful if you can create a page that will reproduce the issue for devs.

Comment 7

[Dieter Ferdinand]

hello,
you must open this site and let it active fore a longer time. this can need 48 hours to consume much memory.

i have activated some more widgets, so the program should eat the memory faster. link under the dashboard for extended informations.

if i use an other tab in the window, it needs longer time to eat the memory, if this is in foreground, i get the problem faster and if i don't close firefox, the tab will crash every time. and first, the tab with the most widgets will crash while out of memory.

i know, it makes no fun to find a bug, which grows very slowly and every time you must wait more then 24 hours to see the problem.

goodby

Comment 8

[Mayank Bansal]

(In reply to Dieter Ferdinand from comment #3)

hello,
here a share-link to the portal:
https://vrm.victronenergy.com/installation/364414/share/1b27618d

This link keeps on loading and doesnt load completely, previously the link would open correctly. Can you check?

Comment 9

[Mayank Bansal]

Andrew, this scenario seems to be something that you may have ideas on.

Comment 10

[Andrew McCreight [:mccr8]]

Just based on the memory report, it looks like the web page is slowly leaking JS arrays. Does this happen in other browsers? You are probably better off reporting this issue to the people maintaining the website. As a work around, you should also be able to reload the page which is hopefully less invasive than restarting the browser.

Comment 11

[Andrew McCreight [:mccr8]]

I'm not sure if this should live in JS because of the JS arrays or maybe Performance or even Site Compat is the right place for it.

Comment 12

[Dieter Ferdinand]

hello,
i will try it with chrome and see what happens.

i make a memory trace with chrome and on this side, much memory was reserverd, but not all was give free again. some variables need 32 byte, if the rest of the memory is released. i will see, how much memory chrome will use tomorrow and if the memory usage will grow.

goodby

Comment 13

[Dieter Ferdinand]

hello,
it seems, that chrome don't have this memory problem, but chrome have other problems. i must reload the page because some content of the widgets is missing.

i will test it over a longer time.

goodby

Comment 14

[Mayank Bansal]

IF you open this link in 15 tabs, then the memory use does increase for the content processes. And if you then close all, the resulting profile has a lot of cycle collection.
https://share.firefox.dev/3S7d87F

Something in that page is leaking memory (that results in long cc), or sharing stuff across multiple tabs or something.

Comment 15

[Mayank Bansal]

I have been able to repro a memory increase of sort.
STR:

1. Open the link in a tab
2. As soon as the tab spinner stops, press f5

Repeat step 2 indefinitely. With each refresh, memory will increase. But when you stop refreshing, the page will cc/gc adn return to the base 300MB RAM.
Here is a profile of the page freeing memory after reaching 4.5GB: https://share.firefox.dev/3vni1AS

Comment 16

[Dieter Ferdinand]

hello,
chrome does not execute the script which get new data from the server, so the site is static and don't have the memory problem.

i will make some tests with firefox again.

if i reload the tab the memory usage was not reduced. i must close the tab and reopen it.

goodby

Comment 17

[Dieter Ferdinand]

hello,
if the site is opened for hours, the memory usage increase over the time to some GB of ram for only one tap.

the only way, to release this memory is by closing the tab. a reload have no effect. and if i reload the page, the browser should free all memory, which ist used before, but it does!

google chrome don't have this memory problem, but chrome have an other problem. i don't know why, but chrome goes back to the start-site of the portal and i don't know why. i will try to find out, if chrome use also much memory, if the site is opened for a longer time, but this is not simple.

goodby

Comment 18

[Dieter Ferdinand]

hello,
chrome don't have this memory problem.

goodby