Ask HN: Why is Chromium a memory hog? Why can't we fix it?
Hoping someone with some architectural knowledge of Chromium can jump in here. I am mainly asking out of curiosity, as other browsers don't seem to suffer from memory bloat in the same order of magnitude.
So, what is it about Chromium that causes it to suck up so much memory? What is difficult about fixing this?
As a further niche, I'm also interested in this from Electron's PoV.
7 comments
[ 2.9 ms ] story [ 26.6 ms ] threadThis also kind of hints at my follow up question around Electron. Electron just uses 2 processes, one Chromium and one Nodejs, but still it has memory problems.
edit Oddly enough I just went and looked. Both Slack and VSCode (electron apps) are actually consuming a relatively reasonable amount of memory (on the order of 100s of MBs each) on my Macbook. Maybe some progress has been quietly made in this area, specific to Electron? Or maybe I'm just desensitized to apps taking up 100s of MBs
Also not everyone has 32G of memory. Most mid range laptops have 8 or 16.