Closed
Bug 1287345
Opened 9 years ago
Closed 1 year ago
Consider running service worker threads at normal priority
Categories
(Core :: DOM: Service Workers, defect, P3)
Core
DOM: Service Workers
Tracking
()
RESOLVED
DUPLICATE
of bug 1563950
| Tracking | Status | |
|---|---|---|
| firefox50 | --- | affected |
People
(Reporter: bkelly, Unassigned)
References
(Blocks 1 open bug)
Details
Currently all non-chrome worker threads are run at low priority:
https://dxr.mozilla.org/mozilla-central/source/dom/workers/RuntimeService.cpp#1620
int32_t priority = aWorkerPrivate->IsChromeWorker() ?
nsISupportsPriority::PRIORITY_NORMAL :
nsISupportsPriority::PRIORITY_LOW;
if (NS_FAILED(thread->SetPriority(priority))) {
NS_WARNING("Could not set the thread's priority!");
}
We should consider running service workers at normal priority since they can be in the hot path for page load.
Updated•9 years ago
|
Priority: -- → P3
| Reporter | ||
Updated•9 years ago
|
Comment 1•6 years ago
|
||
It looks like this was addressed as part of a commit for another bug:
Updated•3 years ago
|
Severity: normal → S3
Comment 2•1 year ago
|
||
This was fixed by bug 1563950 which changed the exact hunk from comment 0 to always try and set normal priority; patch was https://phabricator.services.mozilla.com/D37694
You need to log in
before you can comment on or make changes to this bug.
Description
•