1803988 - firefox using too much memory

Status: RESOLVED INACTIVE

(Core :: Performance, defect)

Description

[dustint213]

Attachment: memory-report.json.gz

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

Steps to reproduce:

I've been trying to open and simply use firefox with multiple tabs, around 5 with different social media websites and forums.

Actual results:

While navigating between them everything would freeze and take a long time to switch between tabs or load anything at all to the point where I would need to shut down the browser and/or restart my laptop and try again. My memory usage with 16gb of ram only running discord and firefox was pushing 95% memory with only one or two tabs open.

Expected results:

The system should be running seamlessly as I am not running any major programs or multiple streaming services at the same time.

Comment 1

[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 2

[Florian Quèze [:florian]]

Thanks for the bug report. We will need a bit more information to understand where the problem comes from. The easiest way to give us at least some information to start with would be to look at about:processes to see which tab is using the memory.

Then to understand what happens, it would be very helpful if you could record a profile and share it. To capture a profile, first go to profiler.firefox.com and click "Enable Firefox Profiler Menu Button". Then click the "Start recording" button. After recording for a few seconds, you can click the profiler toolbar icon to capture the profile. There in the new tab that will open, you can click "Upload local profile".

Comment 3

[Dave Hunt [:davehunt] [he/him] ⌚BST]

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. Details of our performance triage process can be found at https://wiki.mozilla.org/Performance/Triage.