Open
Bug 1513672
Opened 5 years ago
Updated 2 years ago
Twice-reported memory allocations in libimage
Categories
(Core :: Graphics: ImageLib, enhancement, P3)
Tracking
()
ASSIGNED
People
(Reporter: kats, Assigned: aosmond)
References
Details
Attachments
(1 file)
|
3.13 MB,
text/plain
|
Details |
I ran DMD today on a WR-enabled mac build to chase down bug 1491512 a bit more, and the DMD report told me about some twice-reported blocks. Attached is the full log. There are multiple entries near the top for the twice-reported image allocations, with similar-looking stacks.
|
Assignee | |
Updated•5 years ago
|
Flags: needinfo?(aosmond)
|
|
Assignee | |
Updated•5 years ago
|
Priority: -- → P3
|
|
Assignee | |
Comment 1•5 years ago
|
||
Actually this is simpler than I thought it would be. imgFrame::mRawSurface is sometimes the same as imgFrame::mLockedSurface. It isn't complaining about the frame data itself being duplicated, but the surface object wrapping the data. I have a strong sense of deja vu for this for some reason.
Assignee: nobody → aosmond
Status: NEW → ASSIGNED
Flags: needinfo?(aosmond)
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•