4 ms·
I am absolutely flabbergasted by how every fully featured browser is capable of bringing my modern workstation to its knees. Late last year I took a screenshot
by z0r 10y ago
I am absolutely flabbergasted by how every fully featured browser is capable of bringing my modern workstation to its knees. Late last year I took a screenshot of a 32 kb text document running in a tab managed by chrome process with no other tabs to take care of occupying over 1 GB of ram. And when I say text document, I mean a file with a .txt extension with no javascript or anything else going on. The world is wrong!
- bozonil 10y agoThis sounds like a bug. If you can reliably reproduce 32kb txt file taking up 1GB, would you mind filing a bug at https://crbug.com https://crbug.com? Or I can file a bug if you let me know how to reproduce this.
- tracker1 10y agoThe management process, every tab, every extension, and a pool for registered offline workers are all running by firing up chrome... I'd presume there's similar overhead for FF, but not process isolated, that was work in progress iirc. It's not necessarily a bad thing, but can all add up, and it's hard to measuer/add up the separate processes.