Use higher priority messages for notifying parent browsing context about child being loaded.
Categories
(Core :: DOM: Navigation, task, P3)
Tracking
()
People
(Reporter: smaug, Assigned: smaug)
References
Details
(Whiteboard: [not-a-fission-bug])
Attachments
(1 file, 1 obsolete file)
Right now messages to notify that some iframe has been loaded use normal priority messages - and that means they end up being behind everything else there might be on the
normal priority queue.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
(the patch isn't final, but perhaps good enough for some performance testing)
base https://treeherder.mozilla.org/#/jobs?repo=try&revision=d9bd733a69e9cb76f7eff9a6997c438334de9343
patch https://treeherder.mozilla.org/#/jobs?repo=try&revision=bee619cb04b5c6a455db9d9f78dd4c22485c0599
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Olli, do you still want to land this change? Should this bug block enabling Fission in Nightly (milestone M6)?
Assignee | ||
Comment 8•5 years ago
|
||
That patch isn't safe enough. But we probably need to do something here.
Comment 9•5 years ago
|
||
Randell, we should keep this in mind for fission-perf and whether or not we need this right now or later.
Comment 10•5 years ago
|
||
Nika says this work doesn't need to block Fission M6 Nightly. Tracking for Fission Future because this is a speculative fix for perf issues that we don't know exist yet.
Assignee | ||
Comment 11•5 years ago
•
|
||
This is not really speculative. The current setup for load event firing takes very slow paths. Easy to see in profiles.
(But certainly doesn't need to block M6)
Comment 12•5 years ago
|
||
What more would need to be done for this patch to land? What are the safety issues?
Assignee | ||
Comment 13•5 years ago
|
||
the patch changes ordering of things around loading and isn't safe as such.
Assignee | ||
Comment 14•3 years ago
|
||
This is tracked as part of bug 1739417 and is now just a normal performance bug.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Description
•