Closed Bug 883725 Opened 11 years ago Closed 10 years ago

As part of a memory report, output URIs of all images (or something like that)

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1009097

People

(Reporter: justin.lebar+bug, Unassigned)

References

Details

(Whiteboard: [MemShrink:P2])

In B2G, it would be helpful to know which images are currently in memory, and which of those are currently decoded. I'm particularly concerned about doing something like this to help us debug bug 851626, where we have a buildup (a leak?) of gfxImageSurfaces which aren't even tracked in about:memory. Is every gfxImageSurface owned by exactly one RasterImage? If so, maybe it's sufficient to add an "other" memory reporter with output like images/RasterImage(http://foo.com/bar.jpg) 1.25mb gfxImageSurface 2.33mb gfxImageSurface or something like that. I don't really understand yet how all of this memory is owned, so please tell me if I'm nuts.
Summary: As part of a b2g memory report, output URIs of all images (or something like that) → As part of a memory report, output URIs of all images (or something like that)
Whiteboard: [MemShrink]
Whiteboard: [MemShrink] → [MemShrink:P2]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.