1665533 - Memory leak in long-running session

Status: RESOLVED DUPLICATE of bug 1658571

(Firefox :: Untriaged, defect)

Description

[Ben Kero's testing robot]

Attachment: memory-report.json.gz

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

Steps to reproduce:

Use the browser normally for a long time (4 days). Normally means 10-20 tabs.

Actual results:

Memory consumption balloons to consume the majority of my system memory (16GB). It will even run 4+ GB into swap. Happens even when around 10 tabs are open.

Expected results:

Memory consumption should be the same as when starting the browser freshly.

Comment 1

[Ben Kero's testing robot]

Operating system is Fedora 32, build is a built tarball from ftp.mozilla.org run and updated out of my homedir.

The majority of the consumption seems to be from "top(none)" window objects. In all web processes. Referenced in there are many tabs which were previously closed.

Comment 2

[Ben Kero's testing robot]

Attachment: about:support text

Comment 3

[Timea Cernea [:tbabos][inactive]]

Hi Ben, thanks for attaching the memory report. I don't have a Fedora at hand and not really aware of how to build a tarball. Will NI? Andrew in hope he could check out the memory report and help further investigations.

Hey Andrew, could you please take a look at the memory report when you have the time? NI-ed you since Mike Conley says you or erahm have the right expertise for analyzing memory reports.

Comment 4

[Andrew McCreight [:mccr8]]

(In reply to Timea Cernea [:tbabos] from comment #3)

Hey Andrew, could you please take a look at the memory report when you have the time? NI-ed you since Mike Conley says you or erahm have the right expertise for analyzing memory reports.

Sure, I can take a look. FYI, erahm is no longer working at Mozilla so he's no longer the right person to needinfo.

Comment 5

[Andrew McCreight [:mccr8]]

Thanks for the report. I see lots of ghost windows in the memory report, and Disconnect in the list of addons in about:support, so this is almost certainly a dupe of bug 1658571.