1828963 - firefox slowly eats up all memory

Status: RESOLVED DUPLICATE of bug 1828587

(Core :: Performance, defect)

Description

[klaustin]

Steps to reproduce:

1. Open up firefox
2. Wait for 2 to 3 minutes
3. Memory usage as seen in task manager will crawl up until swap (Note: Task manager will report 99% memory usage, but does not point to which process using them. Memory usage goes down after closing Firefox which points out of a conclusion that Firefox is the perpetrator)

Actual results:

Full memory usage and no swap left, firefox left hanging for a while and finally will soft restart

Expected results:

Issue does not exist in previous version, (before version 111/112 [unconfirmed])

Comment 1

[klaustin]

Attachment: about:memory diff from initial run to 2-3 minutes of idle

Comment 2

[klaustin]

Attachment: about:memory

Comment 3

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

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.

Comment 4

[klaustin]

Attachment: about:memory diff from initial run to 2-3 minutes of idle

Comment 5

[klaustin]

similar issue on different operating system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263436

Comment 6

[klaustin]

[new update]

starting firefox in safe mode solves the issue, but I don't see any odd/big difference in memory usage looking at about:memory. Only with the shmem-allocated

Comment 7

[Gian-Carlo Pascutto [:gcp]]

Going to dupe based on last comment.

Comment 8

[Andrew McCreight [:mccr8]]

Could you attach your about:support? You'll want to do "copy raw data to clipboard", paste that into a file and attach it here. Thanks.

Comment 9

[klaustin]

Attachment: about:support

Comment 10

[klaustin]

I notice this bug will only occur if I have more than 1 firefox window opened. I had 5 windows before and not been a problem for a long time since the latest update.

Comment 11

[Andrew McCreight [:mccr8]]

Thanks for the information. If you didn't see in bug 1828587, it looks like the issue is being caused by some interaction of Firefox with the Dark Space Theme. You can try disabling that until we fix the underlying issue in Firefox.