Closed
Bug 1437112
Opened 7 years ago
Closed 7 years ago
10s of GB of heap-unclassified with WebRender enabled
Categories
(Core :: Graphics: WebRender, defect, P1)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox60 | --- | affected |
People
(Reporter: erik, Unassigned)
References
Details
(Whiteboard: [MemShrink])
Attachments
(1 file)
225.63 KB,
application/x-gzip
|
Details |
Twice this week (perhaps coinciding with my upgrade from 59 to 60), I've caught Firefox in the background using 30-60GB of RAM (though more like 1GB resident). I've attached a memory report.
In the latest case, I also noticed 2 content processes "not responding".
Reporter | ||
Updated•7 years ago
|
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Updated•7 years ago
|
Whiteboard: [MemShrink]
Comment 1•7 years ago
|
||
Are you using WebRender or any other non-default thing you can think of?
The main process looks like this:
51,742.58 MB (100.0%) -- explicit
├──50,964.45 MB (98.50%) ── heap-unclassified
Flags: needinfo?(erik)
Updated•7 years ago
|
Summary: Nightly growing huge VSIZEs → 10s of GB of heap-unclassified
Updated•7 years ago
|
Component: Untriaged → General
Product: Firefox → Core
Comment 3•7 years ago
|
||
I'll assume it is related to that given that there are some known issues with leaks...
Updated•7 years ago
|
Summary: 10s of GB of heap-unclassified → 10s of GB of heap-unclassified with WebRender enabled
Reporter | ||
Comment 4•7 years ago
|
||
I'll turn it off and post if it recurs.
Comment 5•7 years ago
|
||
I don't see a couple of GB for the main process but the following is also already more than enough (in case it is the reason of WebRender):
1,175.63 MB (100.0%) -- explicit
├────858.79 MB (73.05%) ── heap-unclassified
Updated•7 years ago
|
Blocks: stage-wr-trains
Priority: -- → P1
Reporter | ||
Comment 7•7 years ago
|
||
It's been fine ever since I turned off WebRender. I've also been updating Nightly every few days, keep in mind.
Flags: needinfo?(erik)
Comment 8•7 years ago
|
||
Okay lets close this for now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•