Hight memory usage on 112.0.2
Categories
(Core :: Performance: General, defect)
Tracking
()
People
(Reporter: an.smodlev, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
433.88 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/112.0
Steps to reproduce:
nothing, no tabs or 1 youtube tab
Actual results:
Hight RAM usage: 1gb and other FF services eating memory too
Expected results:
it would be cool if FF ate not so much, it seems to me that there were no such problems before.
Now this is just an example, but when I develop an application in FF, I simply do not have enough RAM on a working computer with 16GB
<3
| Reporter | ||
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
The memory usage in the report you attached doesn't look like it is super high. There's a lot of heap-overhead which does suggest it used to be much higher.
This also suggests it used to be higher:
587.50 MB ── resident
1,049.19 MB ── resident-peak
1,112.14 MB ── resident-phys-footprint
436.05 MB ── resident-unique
I can't tell what the problem might be with this memory report.
Comment 3•2 years ago
|
||
I just came here to report this bug myself.
I already closed and opened the browser again because it turned useless, without making a screenshot, but memory use was above 12 GB with 5 tabs of Reddit and a couple of small wiki pages open.
Different platform from the original poster's.
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0
Comment 4•2 years ago
|
||
This bug was moved into the Performance component.
:an.smodlev, could you make sure the following information is on this bug?
- For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
- For memory usage issues, capture a memory dump from
about:memoryand attach it to this bug. - Troubleshooting information: Go to
about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
If the requested information is already in the bug, please confirm it is recent.
Thank you.
Comment 5•2 years ago
|
||
(In reply to lorand.l.juhasz from comment #3)
I just came here to report this bug myself.
Please file a new bug for your issue. It is impossible to tell whether you are experiencing the same issue or a different one without more information. There are many possible causes of memory leaks in Firefox, and putting more than one report together in a single bug will only confuse things. Thanks.
Comment 6•2 years ago
|
||
With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again. Details of our performance triage process can be found at https://wiki.mozilla.org/Performance/Triage.
Updated•1 year ago
|
Description
•