Open Bug 1823774 Opened 2 years ago Updated 10 months ago

Improve memory reporting for textures

Categories

(Core :: Graphics, task, P3)

task

Tracking

()

ASSIGNED

People

(Reporter: aosmond, Assigned: aosmond)

References

Details

When looking at memory reports with a lot of memory usage in GPU textures, it isn't clear why this is the case right now. We get some summary statistics here:

https://searchfox.org/mozilla-central/rev/f078cd02746b29652c134b144f0629d47e378166/gfx/thebes/gfxWindowsPlatform.cpp#227

But as I observed in a recent report, this doesn't make it clear to me if we are leaking memory, or not. It would be good to dump more information about:

  • What owns the textures (compositing? specific media elements? canvas?)
  • How many textures there are (how much from the summary stats is unaccounted for?)
  • What kind of textures are they
  • How long have the textures been alive
  • When were they last used

I may not resolve all of those questions for all sources in this bug, but I would like to begin the work to do so and iterate over time.

See Also: → 1818982
You need to log in before you can comment on or make changes to this bug.