Open Bug 1509084 Opened 6 years ago Updated 2 years ago

High CPU. network traffic and memory usage when open Newtab page if you have opened a problematic/ huge game page in the past

Categories

(Firefox :: New Tab Page, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

Tracking Status
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- wontfix
firefox67.0.1 --- wontfix
firefox68 --- wontfix
firefox81 --- wontfix

People

(Reporter: alice0775, Unassigned)

References

(Blocks 2 open bugs, )

Details

(Keywords: memory-footprint, reproducible, Whiteboard: [thumbnails])

+++ This bug was initially created as a clone of Bug #1384094 Comment 33+++ CPU I can reproduce the issue on Nightly65.0a1 windows10. The memory usage 3GB and more, CPU almost 100% 2/4core. Steps To Reproduce: 1. Launch Firefox using a fresh profile. 2. Open http://www.mozdev.org/projects/nav.html 3. Quit the browser as soon as the page starts to appear. And then restart it. - Make sure to check the CPU, network traffic and memory usage Actual Results: Even if there are about:home and Newtab page, browser consumes High CPU and memory. Expected Results: Very low CPU and memory usage. because, only one tab home(new tab page) Setting browser.newtabpage.activity-stream.feeds.topsites = false will fix the problem.
Severity: major → normal
Priority: P1 → --
I think, the thumbnails should be taken while the page is displaying and PC is idle, not while the Home tab (new Tab) is displayed.
Priority: -- → P3

I can still reproduced on Nightly68a1 :(

This can likely be partly addressed by bug 1162698 (put a time limit on thumbnailing)

This page is also
https://treeherder.mozilla.org/#/jobs?repo=autoland

STR:
Clear Recent History, every thing
Open https://treeherder.mozilla.org/#/jobs?repo=autoland and close this tab when tab spinner stops.
Restart Browser

AC:
High CPU for 10-20second (maybe depended with network speed/CPU power) even if there is New Tab only

Component: Activity Streams: Newtab → New Tab Page

Worsened in 80beta and 81.0a1, peak memory usage is more than 4GB :(

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.