High Memory and CPU Usage
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
People
(Reporter: rontilby, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
I left firefox running overnight with two windows open and a total of 3 tabs.
Actual results:
This morning Firefox was using > 4GB and consuming > 20% CPU.
Expected results:
Memory consumption should have been much less and firefox should not have been consuming more than a few % of CPU when sitting idle.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 2•4 years ago
|
||
Firefox nightly 100.0a1 (2022-03-30) (64-bit) on Windows 10
open https://www.familysearch.org/eurona/feed/home
login
Wait 8 hours
Firefox memory consumption climbs to 4.5 GB per windows task manager
Memory consumption appears to be concentrated in js-main-runtime
4,132.20 MB (100.0%) -- js-main-runtime
├──3,985.45 MB (96.45%) -- realms
│ ├──3,979.66 MB (96.31%) -- classes/objects
│ │ ├──3,973.13 MB (96.15%) ── gc-heap
│ │ └──────6.52 MB (00.16%) ++ malloc-heap
│ └──────5.80 MB (00.14%) ++ (5 tiny)
├─────68.19 MB (01.65%) -- zones
│ ├──47.44 MB (01.15%) ── gc-heap-arena-admin
│ └──20.75 MB (00.50%) ++ (15 tiny)
├─────65.30 MB (01.58%) -- gc-heap
│ ├──64.06 MB (01.55%) ── chunk-admin
│ └───1.23 MB (00.03%) ++ (2 tiny)
└─────13.25 MB (00.32%) ── runtime
4,100.21 MB (100.0%) -- js-main-runtime-gc-heap-committed
├──4,094.05 MB (99.85%) -- used
│ ├──3,982.54 MB (97.13%) -- gc-things
│ │ ├──3,973.13 MB (96.90%) ── objects
│ │ └──────9.41 MB (00.23%) ++ (10 tiny)
│ ├─────64.06 MB (01.56%) ── chunk-admin
│ └─────47.44 MB (01.16%) ── arena-admin
└──────6.17 MB (00.15%) ++ unused
| Reporter | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Over to JS land given the memory report details.
Comment 5•4 years ago
|
||
The symptoms of this look exactly the same as Bug 1675837. We unfortunately don't have a great answer for this yet.
Two things would be helpful:
-
If you could open Dev-tools ( Tools -> Browser Tools -> Web Developer Tools), then click the Memory tab, and take a snapshot. In the leftmost column there will be an option to save it; if you could upload that somewhere and link it here we could try to make sense of that to see if this is a JS engine issue or not.
-
If you could gather a profile using https://profiler.firefox.com/ for about 5-10 minutes on the page and then share it here.
Description
•