Closed Bug 1110024 Opened 10 years ago Closed 9 years ago

[e10s] Slow performance of back button with complex site

Categories

(Core :: DOM: Content Processes, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
e10s + ---

People

(Reporter: billm, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: perf)

STR: 1. Visit the given URL. 2. Click the "earth" button and change some parameters several times (to accumulate history). 3. Hold down on the back button. The menu will take a long time to come up and the UI will be frozen during that time. We're using CPOWs here, but I wonder why it's so slow. We're continuing to draw the web content the whole time, so the content process is making progress. Perhaps the content process only answers one CPOW per frame and we're sending a lot of CPOWs to build the history menu? It looks like we use about 6 CPOW messages per menu item. I only get a few frames per second, so this is conceivable.
Blocks: e10s-perf
tracking-e10s: --- → +
Keywords: perf
We're not using cpows anymore since bug 1148505. Maybe we could retest.
This menu comes up at a good speed for me from just looking at it. I suspect we can close this.
Works pretty decently for me as well. Bill, do you think we can close this?
Flags: needinfo?(wmccloskey)
Thanks.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(wmccloskey)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.