Re:Mozilla lays off 70
by scriptsmith on Wednesday January 15, 2020 @09:40PM
(#22061231)
It could be a genuine leak, but it sounds an awful lot like Firefox using 28 GiB of virtual memory.
Firefox often appears to use large amounts of memory in top / htop, but I believe that's just reported address space allocations. The RES column gives a more accurate depiction of memory usage.
Re:Mozilla lays off 70
by zelly on Wednesday January 15, 2020 @10:24PM
(#22061416)
It was real memory. I know the difference. I only noticed because I got an OOM error in my Java program and X11 froze, couldn't use my mouse. This happened multiple times with different heavy duty JS websites, particularly SPAs.
Firefox often appears to use large amounts of memory in top / htop, but I believe that's just reported address space allocations. The RES column gives a more accurate depiction of memory usage.