Closed Bug 1903398 Opened 9 months ago Closed 3 months ago

Ram Usage bug

Categories

(Core :: Graphics: WebRender, defect)

Firefox 127
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: zarqorn, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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

Steps to reproduce:

After leaving the browser open for a few hours the ram usage balooned to 30 GB (all available ram)
Open tabs in attachement below.

Actual results:

The ram usage increased to ~30 GB (32 is available in the system)

Expected results:

Not that

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

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core

I created a meta bug for these kinds of issues with some instructions to gather additional info to figure out where the leak is occurring, can you take a look at that guide? https://bugzilla.mozilla.org/show_bug.cgi?id=1902566

Knowing where the leak is occurring is essential and sometimes it depends on GPU driver version so we need at least the about:support and preferably the other info it describes.

From what you said in the opening comment I am guessing this is growing without interaction?

Severity: -- → S2
Flags: needinfo?(zarqorn)

Flagging as stalled until we receive a response from the reporter.

Keywords: stalled

In the interest of tidying up, I'm closing this bug due to lack of response.

Status: UNCONFIRMED → RESOLVED
Closed: 3 months ago
Flags: needinfo?(zarqorn)
Resolution: --- → INACTIVE

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit BugBot documentation.

Keywords: stalled
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: