Low priority timers should be dispatched at a priority lower than normal
Categories
(Core :: XPCOM, enhancement)
Tracking
()
People
(Reporter: florian, Assigned: florian)
Details
Attachments
(1 file)
Currently all timers are dispatched at a normal priority. This is confusing as the timer API exposes the following types that sounds like they would cause the timer callback to run at a lower priority:
- TYPE_REPEATING_SLACK_LOW_PRIORITY
- TYPE_ONE_SHOT_LOW_PRIORITY
| Assignee | ||
Comment 1•3 years ago
|
||
| Assignee | ||
Comment 2•3 years ago
|
||
I'm not sure what the actual priority should be. The attached patch uses EventQueuePriority::Low, but I mostly put it up there for discussion.
I think what low priority means in the nsITimer API isn't very well defined, so it's probably a matter of guessing what behavior the developers who used them wanted to have.
Comment 3•3 years ago
|
||
lower priority timers don't have anything to do with priority on the target thread. They are there just for idle handling.
Perhaps their name should be changed though.
Comment 4•3 years ago
|
||
I'm fine adding some mechanism to lower the priority, but let's not break the existing API.
Description
•