Open Bug 1181333 Opened 9 years ago Updated 1 year ago

set_selectedIndex() @ tabbrowser.xml:6105 triggers a frame during tab switch


(Firefox :: Tabbed Browser, defect, P3)




Tracking Status
e10s + ---
firefox42 --- affected


(Reporter: BenWa, Assigned: mconley)


(Blocks 1 open bug)


NOT A PERF PROFILE! I got a 'profile' logging everything that is hitting PresContext when changing:

Looks like 'set_value() @ autocomplete.xml:269' is responsible for the first extra frame we see during tab switch time. This is hurting our tab switch time because we're painting an intermediate frame that doesn't include the tab content.

In optimized builds this function still shows up as also taking a lot of direct CPU time in addition to trigger the refresh driver to run later.
Blocks: 1180916
That autocomplete.xml binding is certainly the one belonging to the URL bar, which we update synchronously with the URL of the tab that we're switching to.
One thing we might want to try is to not update the URL bar (and the rest of the navigation-toolbox) until the tab frame is ready to paint. That would, theoretically, allow us to avoid painting at _least_ one frame and blocking the main process, which gives the content process greater lee-way in sending sync messages.

We'd have to come up with some kind of solution for the case where the tab we're switching to needs to have the URL bar focused so as to not lose any key events.
Blocks: 1174776
tracking-e10s: --- → ?
BenWa, to the best of my recollection I started working on suppressing paints during tab switch which improved tab switching at first. Then other stuff landed and it was a wash. So... I guess I'm asking if this is still a problem.
Flags: needinfo?(bgirard)
If we implement paint suppression properly then all sub bugs of bug 1180916 should be fixed since we can't paint by definition. AFAIK it still hasn't shipped so this bug is likely still here.
Flags: needinfo?(bgirard)
Assignee: nobody → mconley
Priority: -- → P2
Moving to p3 because no activity for at least 1 year(s).
See for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.