3 ms·
Installed the new firefox, had 1 tab running for a few days which had allocated more than 10gb of virtual memory. I had high hopes but im sticking with chrome.
by nopit 9y ago
Installed the new firefox, had 1 tab running for a few days which had allocated more than 10gb of virtual memory. I had high hopes but im sticking with chrome.
- DigitalJack 9y agoForgive my ignorance, but does having X amount of virtual memory allocated necessarily correspond to physical memory (and storage for that matter?)
- tjoff 9y agoIt does not (but it is a big problem for 32 bit applications where you quickly run out of addressable memory).
- deathanatos 9y agoNo, it doesn't necessarily correspond. It could be an indicator, though. RSS would be more useful, IMO. That said, even if the poster is correct, it isn't necessarily wrong either. AFAICT, nothing stops JS on a page from allocating that much memory, and "leaking" it (e.g., holding on to the JS object, maybe accidentally in a giant list, and not making use of it). It isn't the browser's fault if JS is actually "using" that much RAM.
- deleted 9y ago[deleted]