Content process large CPU / Memory after new tab page opened with a specific page in history
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: yfdyh000, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: memory-footprint, memory-leak, top-memory-leak, Whiteboard: [fxperf:p3])
Attachments
(7 files)
Comment 1•7 years ago
|
||
Updated•7 years ago
|
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
Updated•7 years ago
|
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Comment 8•7 years ago
|
||
Comment 9•7 years ago
|
||
Updated•7 years ago
|
Updated•7 years ago
|
Comment 10•7 years ago
|
||
Comment 11•7 years ago
|
||
Comment 12•7 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 13•2 years ago
|
||
The page at comment 6 is still causing a large memory increase, we don't have screenshots anymore in the New Tab page (and more in general we can't find any use in Firefox, though new Mozilla projects are using thumbnails), but the page is still causing the bug.
This looks related to page loading issues, rather than Firefox itself, we'd appreciate your help into figuring out why the load is consuming so many resources.
Updated•2 years ago
|
Comment 14•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Comment 15•2 years ago
|
||
The page in comment 6 is 404 now, so I don't know if it still endlessly leaks memory, but unfortunately endlessly leaking memory is always going to cause performance problems. It seems that the removal of thumbnailing should have at least improved the situation.
Description
•