Closed Bug 1480287 Opened 6 years ago Closed 6 years ago

Possible memory leak

Categories

(Core :: Graphics: WebRender, defect, P4)

x86_64
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox63 --- disabled

People

(Reporter: rowbot, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Attached file Memory Report (deleted) —
Many apologies for the vague title. I happened to notice Nightly was getting sluggish and when I checked task manager, it said Nightly was using 2.5 GB for the 4 (Github) tabs I had opened. I've attached a memory report with this bug. I scanned over it and noticed that the GPU Process has 4,120.28 MB (99.42%) ── heap-unclassified listed. I have Webrender enabled, so filing here seems like a good place to start. Please let me know if I can provide anymore information.
Attached file about:support (deleted) —
Priority: -- → P2
Priority: P2 → P3
We have new memory reporters. Can you reproduce this and attach a new report?
Flags: needinfo?(smokey101stair)
build 20180801100116 was affected by bug 1495242.
Attached file memory report 2 (deleted) —
Here is a new memory report. I'm not seeing numbers quite as bad as those in my original report, but I'm still seeing ~400 MB of heap-unclassified.
Flags: needinfo?(smokey101stair)
Our memory usage is much better now. Can you re-measure for us?
Flags: needinfo?(smokey101stair)
Priority: P3 → P4
I am no longer seeing such high heap-unclassified memory usage. I'm going to close this.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(smokey101stair)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: