Open Bug 1370998 (wr-memory) Opened 3 years ago Updated 18 days ago

[meta] Tracking bug for WebRender memory issues

Categories

(Core :: Graphics: WebRender, enhancement, P5)

enhancement

Tracking

()

Tracking Status
firefox56 --- unaffected
firefox57 --- unaffected

People

(Reporter: jrmuizel, Unassigned)

References

(Depends on 5 open bugs, 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.
Keywords: perf
Priority: -- → P3
Whiteboard: [gfx-noted]
Priority: P3 → P2
Whiteboard: [gfx-noted] → [wr-mvp] [gfx-noted]
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]
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.
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.
Bug 1479939 might also help here.
Depends on: 1479939
No longer depends on: 1479336
Priority: P3 → P2
Metabug -> P5.
Priority: P2 → P5
Alias: wr-memory
Summary: [meta] WebRender uses up too much memory → [meta] Tracking bug for WebRender memory issues
Depends on: 1493196
Depends on: 1495162
Depends on: 1495242
Depends on: 1495661
Whiteboard: [gfx-noted] → [gfx-noted][MemShrink:meta]
Depends on: 1511354
Depends on: 1547070
Depends on: 1654013, 1660407
Blocks: wr-perf
No longer blocks: stage-wr-trains
Depends on: 1667535
Depends on: 1655176
Depends on: 1668837
You need to log in before you can comment on or make changes to this bug.