Decompose explicit/gfx/heap-textures

NEW
Unassigned

Status

()

Core
Graphics: Layers
P3
normal
a year ago
4 months ago

People

(Reporter: jrmuizel, Unassigned, NeedInfo)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

a year ago
A user reports having a very high explicit/gfx/heap-textures.
https://www.reddit.com/r/firefox/comments/4uz7s1/reddit_takes_up_to_13_gb_of_ram_with_45_tabs_open/

We should try to separate out heap-textures into different pieces so that reports like this are more actionable.
(Reporter)

Updated

a year ago
Flags: needinfo?(jmuizelaar)
How about we pass an enum to all of the texture creation methods (like TextureClient::CreateForDrawing, etc.)?
The enum could have values like Content, Tile, Canvas, Video, Plugin, ScreenShot, etc.
Whiteboard: [gfx-noted]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.