Open
Bug 1290100
Opened 8 years ago
Updated 2 years ago
Decompose explicit/gfx/heap-textures
Categories
(Core :: Graphics: Layers, defect, P3)
Core
Graphics: Layers
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned, NeedInfo)
Details
(Whiteboard: [gfx-noted])
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•8 years ago
|
Flags: needinfo?(jmuizelaar)
Comment 1•8 years ago
|
||
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.
Updated•8 years ago
|
Whiteboard: [gfx-noted]
Updated•7 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•