2 ms·
It's rather obvious that chrome isn't intended for heavy duty as the tab bar becoming unusable above ~20 tabs. So I use multiple windows instead and max out 8 g
by posterboy 9y ago
It's rather obvious that chrome isn't intended for heavy duty as the tab bar becoming unusable above ~20 tabs. So I use multiple windows instead and max out 8 gb pretty quickly. I'm just glad it backs up dynamic content like edited form fields before those tabs get crashed to free up space. Also, it's quick to reach 7.9 gb, but goes a long way on that last ~100 mb. But of course a long running js leaking memory on some news site can bring it down.
Two times in a month the login manager crashed and I couldn't get back in from lock screen without killing a few processes manually on console. I'm going back to Firefox with noscript and tree style tabs, as soon as I finished working on all those open tabs ... so, probably never. I don't want to miss the history search and security of chromium.
So I should learn to use the history sidebar instead of tree tabs, and use the tab bar like a ring buffer, not a stack. And I should try deactivating js globaly, if there is a whitelist built-in.