Closed Bug 1757077 Opened 9 months ago Closed 29 days ago

Firefox starts consuming >10GB RAM when idle

Categories

(Core :: Performance, defect)

Firefox 97
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: pjrzto462, Unassigned, NeedInfo)

Details

Attachments

(1 file)

889.76 KB, application/x-zip-compressed
Details
Attached file attachment.zip

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

Steps to reproduce:

  1. Start Firefox
  2. Open a couple of tabs on the same or diffrent websites (actual visited website per tab does not matter)
  3. Let firefox idel for 2-3h in the background

After a while firefox slows down, temporarily freezes.
A look in the windos taskmanager shows, fiefox consuming up to 10GB of RAM, sometimes even more. (See: Screen_WindowsTaskManager)
Interestingly this behaviour can't be viewd in the internal firefox TaskManager (See: Screen_FFtaskManager)

Attached are:

  • Windows TaskManager scereenshot
  • Firefox TaskManager screenshot
  • Frefox memory report
  • about:support information

Actual results:

  1. Single Firefox process hogging >8GB of RAM without beeing related to any actual web-content.

Expected results:

I guess firefox is not supposed to allocate that much memory?

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

Component: Untriaged → Performance
Product: Firefox → Core

Could you try running Firefox in troubleshoot mode to see if you are still able to reproduce the problem. This will help us to determine if one or more of your addons are causing the performance issue.

Here's an article on enabling troubleshoot mode: https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-4troubleshoot-modesf5safe-modesf

Flags: needinfo?(pjrzto462)

With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again.

Status: UNCONFIRMED → RESOLVED
Closed: 29 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.