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

Status: RESOLVED FIXED

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

Description

[Markus Stange [:mstange]]

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.

Comment 1

[tyaremco]

Is this issue exclusive to e10s?

Comment 2

[Markus Stange [:mstange]]

Yes, we're already using TextureClientPools correctly for tab switching in non-e10s Firefox.

Comment 3

[Sylvestre Ledru [:Sylvestre]]

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

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 5

[Gregory Pappas [:gregp]]

Is this still a concern?

Comment 6

[Markus Stange [:mstange]]

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