Open Bug 1788853 Opened 3 months ago Updated 24 days ago

Slow shut down

Categories

(Core :: Performance, defect)

Firefox 104
defect

Tracking

()

UNCONFIRMED

People

(Reporter: zounp, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

Start Firefox on Debian 10 Buster
Open 200 tabs
Firefox uses about 481 MB
Shutdown Firefox
The memory usage goes up to almost 10GB. It takes Firefox 4:13 minutes to shut down

Actual results:

See above

Expected results:

Faster shutdown with less memory usage

The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Performance
Product: Firefox → Core

Even with 32 pinned tab and 58 regular tabs open it takes Firefox 104.0.2 4 minutes and a memory increase from about 600 MB to 8 GB to shutdown.

Mccr8, since I can't request an about:memory report from the user, any chance you have heard of this bug before or know what the appropriate component is? Otherwise some form of shutdown profile might help. Julien, do you know how the user could grab a profile of the situation occurring?

Flags: needinfo?(felash)
Flags: needinfo?(continuation)

I have not, sorry. Hopefully a shutdown profile would show where the allocations are coming from...

Flags: needinfo?(continuation)

This requires starting firefox with the environment variable MOZ_PROFILER_SHUTDOWN=<filename> set, where <filename> is the name of the file where the recorded profile should be saved.
Then start the profiler as usual.

Given the length of the scenario I would suggest reducing the interval to something such as 10ms or maybe even 100ms before starting, this can be done in the configuration page about:profiling before starting the profiler from the popup.

Please tell me if you need any more information about this!

Flags: needinfo?(felash)

Although that before https://bugzilla.mozilla.org/show_bug.cgi?id=1528859 is fixed (that is... in tomorrow's nightly), we'll have only the profile for the main process in the end. But that may be good enough for this bug, who knows?

(In reply to Julien Wajsberg [:julienw] from comment #5)

This requires starting firefox with the environment variable MOZ_PROFILER_SHUTDOWN=<filename> set, where <filename> is the name of the file where the recorded profile should be saved.
Then start the profiler as usual.

Given the length of the scenario I would suggest reducing the interval to something such as 10ms or maybe even 100ms before starting, this can be done in the configuration page about:profiling before starting the profiler from the popup.

Please tell me if you need any more information about this!

Hopefully the reporter is able to provide this.

Flags: needinfo?(zounp)
You need to log in before you can comment on or make changes to this bug.