Open
Bug 1513053
Opened 7 years ago
Updated 3 years ago
Image memory reporter can produce reports with conflicting kind values
Categories
(Core :: Graphics: ImageLib, defect, P3)
Tracking
()
NEW
People
(Reporter: kats, Assigned: aosmond)
References
Details
Attachments
(2 files)
I got 2 memory reports from about:memory on Mac and tried diffing them. It fails at [1] due to the reporter at [2]. I'm attaching the reports.
[1] https://searchfox.org/mozilla-central/rev/fd62b95c187a40b328d9e7fd9d848833a6942b57/toolkit/components/aboutmemory/content/aboutMemory.js#719
[2] https://searchfox.org/mozilla-central/rev/fd62b95c187a40b328d9e7fd9d848833a6942b57/image/ImageMemoryReporter.cpp#121
|
Reporter | |
Comment 1•7 years ago
|
||
|
|
Reporter | |
Updated•7 years ago
|
Summary: Image memory reporter can produce reports with conflicting kind vales → Image memory reporter can produce reports with conflicting kind values
|
Assignee | |
Comment 2•7 years ago
|
||
Hmm, I wonder if it is somehow confusing different surface entries in the diff... they should never be different for the same actual surface.
Assignee: nobody → aosmond
Priority: -- → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•