Closed Bug 1176007 Opened 9 years ago Closed 1 year ago

[e10s] Switching tabs shouldn't need to allocate memory for layer textures

Categories

(Core :: Graphics: Layers, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox41 --- affected

People

(Reporter: mstange, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: gfx-noted)

One of the big reasons for e10s tab switching being slow is the fact that we allocate new TextureClients for layer contents (+ the shmems for them) whenever we switch tabs.

We have infrastructure for reusing TextureClients (TextureClientPool) but we're not making use of it for tab switching.

There might be multiple steps along the way of fixing this so I'm filing this bug as a tracking bug and filing new bugs for the actual work that needs to be done.
Summary: [meta] Switching tabs shouldn't need to allocate memory for layer textures → [meta] [e10s] Switching tabs shouldn't need to allocate memory for layer textures
Depends on: 1176011
Is this issue exclusive to e10s?
Yes, we're already using TextureClientPools correctly for tab switching in non-e10s Firefox.
Whiteboard: gfx-noted
Priority: -- → P2
Assignee: nobody → gwright
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: gw → nobody

Is this still a concern?

Flags: needinfo?(mstange.moz)

Happily WebRender solved this one completely! We don't allocate big surfaces for painting in content processes any more.

Status: NEW → RESOLVED
Closed: 1 year ago
Depends on: fixed-by-webrender
Flags: needinfo?(mstange.moz)
Keywords: meta
Resolution: --- → FIXED
Summary: [meta] [e10s] Switching tabs shouldn't need to allocate memory for layer textures → [e10s] Switching tabs shouldn't need to allocate memory for layer textures
You need to log in before you can comment on or make changes to this bug.