Animated newtab background images consume CPU even when not in the foreground
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley, NeedInfo)
References
Details
Attachments
(1 file)
STR:
- Download this GIF image: https://drive.google.com/file/d/1xvEHMjUX77D5wfEt3Ppjtb10iksP5Jxe/view?usp=sharing
- In a new profile, set that image as the custom background
- Open several new tabs
- Visit about:processes, and look at the CPU usage of "About pages"
ER:
When newtab is backgrounded, we should try to avoid consuming any CPU except to prepare the next newtab opening.
AR:
It appears that the images that are animating are still causing the CPU to be consumed.
We might be able to easily solve this by setting the imageAnimationMode on the document to kDontAnimMode when in the background, and then set it to kNormalAnimMode when foregrounded.
| Assignee | ||
Updated•7 months ago
|
| Assignee | ||
Comment 1•7 months ago
|
||
| Assignee | ||
Comment 2•7 months ago
|
||
This is fairly speculative, but certainly seems to drop the CPU usage way down when I have many tabs open.
This doesn't cover the preloaded newtab case, since that newtab thinks it is visible. If that is something we also want to solve, we may have reached the point where we accept the patch in bug 1548683, which makes the preloaded newtab not think it is visible.
Comment 3•7 months ago
|
||
Why is it that the refresh driver doesn't know that the document is background and so throttles the ticking?
Comment 4•7 months ago
|
||
The severity field is not set for this bug.
:thecount, could you have a look please?
For more information, please visit BugBot documentation.
Comment 5•1 month ago
|
||
See also bug 1972210
Updated•1 month ago
|
Comment 7•1 month ago
|
||
| bugherder | ||
Description
•