Closed
Bug 1615607
Opened 4 years ago
Closed 4 years ago
Consider to always treat high priority runnables as the highest priority runnables
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla75
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
(Regressed 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
Currently PrioritizedEventQueue tries to avoid starving non-high priority runnables.
But given that high priority is for vsync only, we could perhaps simplify thread level implementation and avoid starvation in RefreshDriver.
|
Assignee | |
Comment 1•4 years ago
|
||
Depends on D62033
|
|
Assignee | |
Comment 2•4 years ago
|
||
|
||
Updated•4 years ago
|
Attachment #9126761 -
Attachment is obsolete: true
|
|
Assignee | |
Comment 3•4 years ago
|
||
|
|
Assignee | |
Comment 4•4 years ago
|
||
The patch removes the tad odd interleave behavior from the main thread and makes RefreshDriver to give
at least a tiny bit time for non-high priority tasks.
Given the recent change to have similar block-until behavior in child and parent process, this should work
consistently in all the processes.
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/95fe1470b371 Consider to always treat high priority runnables as the highest priority runnables, r=farre
|
||
Comment 6•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in
before you can comment on or make changes to this bug.
Description
•