3 ms·
It's not chrome's bloat, it's Slack that's for some reason broken. I don't have such problems with VSCode for example. Also it's reusing already opened Chrome i
by methyl 10y ago
It's not chrome's bloat, it's Slack that's for some reason broken. I don't have such problems with VSCode for example. Also it's reusing already opened Chrome instance which should make memory usage more optimized.
- lawnchair_larry 10y agoSlack might be making it worse, but come on. Chrome is huge. Check out the memory and cpu usage of VS Code, and compare that to any other text editor. An instance of chrome just for text editing blows my mind.