4 ms·
I generally find Chrome likes to start falling over around the 3.5GB mark (as measured by chrome://memory) - larger images stop loading, pages stop rendering pr
by Freaky 14y ago
I generally find Chrome likes to start falling over around the 3.5GB mark (as measured by chrome://memory) - larger images stop loading, pages stop rendering properly, and eventually it can end up crashing. Address space fragmentation I'm guessing.
This isn't helped much by Chrome's aggregate memory use being about 10x higher than other browsers. Takes a good 2-300 tabs in Opera to break 4GB, takes more like 20-30 in Chrome.