1785209 - Firefox nightly main process has massive memory consumption (15-20gb)

Status: RESOLVED FIXED

(Core :: Memory Allocator, defect)

Description

[nova_2k1]

Attachment: memory-report.json.gz

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

no STR, happend only once till now. Nightly from 14.08.22
I randomly noticed very high memory consumption, while checking process explorer for something else.

I grabbed an about:memory report, while almost crashing firefox.

Comment 1

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

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

Comment 2

[nova_2k1]

Attachment: memory-report 2.json.gz

Comment 3

[nova_2k1]

Attachment: memory-report 3.json.gz

Comment 4

[nova_2k1]

some more logs, less severe this time.

An early indicator for this issue happening seems to be that some favicons stop loading.

Comment 5

[Arthur K. (he/him)]

Hi,

Chiming in here because I noticed some major hanging and large mem use recently with 105.0b1. Can you guys take a peek at https://bugzilla.mozilla.org/show_bug.cgi?id=1778214#c17 and tell me if it seems in the same wheelhouse as this memory leak / dev tools hanging?

Comment 6

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

The severity field is not set for this bug.
:glandium, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 7

[Ray Kraesig [:rkraesig]]

Attachment: Graph of main-process OOM crashes per hour on x64 Windows Nightly by build date

Similar behavior has also been unofficially reported by :nika, and a graph of Nightly main-process OOM crashes shows a significant increase starting around 2022-08-12 or -13.

Comment 8

[Ray Kraesig [:rkraesig]]

OOM rates reverted to normal as of August 31. Their rise and fall coincide with the application and reversion of patch D154141 for bug 965392.

Although (AFAIK) the precise mechanism hasn't been identified, the issue seems to be resolved. Closing accordingly.