Closed
Bug 1495032
Opened 7 years ago
Closed 7 years ago
Account for tab warming and multiple "active" tabs when adjusting process priority
Categories
(Core :: DOM: Content Processes, enhancement)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: alexical, Assigned: alexical)
References
Details
(Whiteboard: [fxperf:p1])
Attachments
(1 file)
When we switch tabs, we adjust the process priority at the end of SetDocShellIsActive. We should really adjust it in SetRenderLayers to account for tab warming.
Additionally, when a tab is actually selected it seems like we should "cool off" the visible tab, decreasing its priority since it's about to be hidden.
|
Assignee | |
Comment 1•7 years ago
|
||
Taking this real quick since I think it's fairly simple.
Assignee: nobody → dothayer
Status: NEW → ASSIGNED
Whiteboard: [fxperf:p1]
|
|
Assignee | |
Comment 2•7 years ago
|
||
Our current prioritization mechanism doesn't account for tab
warming, or for the fact that the current tab should be
deprioritized. This corrects that.
|
||
Comment 3•7 years ago
|
||
Comment on attachment 9012958 [details]
Bug 1495032 - Proactively adjust tab priority on switch r=mconley
Mike Conley (:mconley) (:⚙️) has approved the revision.
Attachment #9012958 -
Flags: review+
Pushed by dothayer@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bcdbc281a48d
Proactively adjust tab priority on switch r=mconley
|
||
Comment 5•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•