"Forget about this site" function uses all system RAM
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: hamesg, Unassigned)
References
Details
Attachments
(1 file)
|
180.42 KB,
image/jpeg
|
Details |
Picture of system monitor (taken from a phone since the system had froze)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
Used "Forget about this site" function in the history sidebar on a very commonly browsed domain such as gitHub.com or duckduckgo.com
I ran into this a bit earlier and commented in https://bugzilla.mozilla.org/show_bug.cgi?id=903777#c23 but I believe it is better as a separate issue.
Actual results:
Firefox uses around 200-300% CPU and uses consumes around +100MB/s of RAM for a few minutes it the system runs out of memory. For me this is 11GB of RAM.
Before the test Firefox was using 800MB of RAM (2 idle tabs and 1 new-page tab) and the system froze at 8.1GB of RAM (see picture).
I imagine it would finish if I had enough RAM (not sure how much it needs) because it is able to complete the function for sites that I visit less frequently. I use GitHub for work so I imagine there are hundreds of thousands of history items in there...
Expected results:
It shouldn't crash the computer and shouldn't use so much RAM.
Oh I should mention that the "Disk read total" and "Disk write total" values of the system monitor did not change at all while it was doing its work.
I've also had this computer for less than one year so there are less than a year of history items.
Ah this might be duplicate. I searched "Forget about this site RAM" on Bugzilla and got no results so I made this bug, but I've since found https://bugzilla.mozilla.org/show_bug.cgi?id=734643#c41 where a few people describe FF eating 16GM of RAM and causing OOM.
Feel free to close this but I'm not sure how new comers are supposed to keyword search as bug 734643 does not match a search for RAM or for "Forget about this site" feature...
|
||
Comment 4•3 years ago
|
||
Hi hamesg,
Unfortunately, seems like this is a known issue, as you also mentioned the bug and this would be a duplicate of that.
There are some instructions given on how this can be avoided (more or less) in this bug Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1699600#c4.
I'll have to close this report since it was already filed several times, but thank you very much for taking the time into reporting it.
Description
•