Closed
Bug 1370998
(wr-memory)
Opened 7 years ago
Closed 9 months ago
[meta] Tracking bug for WebRender memory issues
Categories
(Core :: Graphics: WebRender, enhancement, P5)
Core
Graphics: WebRender
Tracking
()
RESOLVED
DUPLICATE
of bug 1549410
Tracking | Status | |
---|---|---|
firefox56 | --- | unaffected |
firefox57 | --- | unaffected |
People
(Reporter: jrmuizel, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: meta, perf, Whiteboard: [gfx-noted][MemShrink:meta])
On macOS with webrendest enabled and layers.force-active. We'll eventually use up 768MB of RGBA texture cache when this happens performance goes in the trash.
Updated•7 years ago
|
Updated•7 years ago
|
Blocks: stage-wr-trains
Updated•7 years ago
|
Priority: P3 → P2
Whiteboard: [gfx-noted] → [wr-mvp] [gfx-noted]
Updated•7 years ago
|
status-firefox56:
--- → unaffected
status-firefox57:
--- → unaffected
Updated•7 years ago
|
Keywords: meta
Priority: P2 → --
Summary: WebRender uses up too much memory → [meta] WebRender uses up too much memory
Whiteboard: [wr-mvp] [gfx-noted] → [gfx-noted]
Updated•7 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
I'm going to hijack this bug into a general memory usage metabug. If the thing in comment 0 is still a problem we can spin it out into a new concrete bug.
Comment 2•6 years ago
|
||
https://github.com/servo/webrender/pull/2941 might help, it makes it more likely for a texture cache entry to get evicted soon when it's image key is deleted. That said the eviction strategy in the texture cache does not take available/consumed memory into account in any way so there must be ways to improve there.
Reporter | ||
Updated•6 years ago
|
Priority: P3 → P2
Updated•6 years ago
|
Alias: wr-memory
Summary: [meta] WebRender uses up too much memory → [meta] Tracking bug for WebRender memory issues
Updated•6 years ago
|
Whiteboard: [gfx-noted] → [gfx-noted][MemShrink:meta]
Updated•4 years ago
|
Updated•4 years ago
|
Updated•2 years ago
|
Severity: normal → S3
Updated•9 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•