logoalt Hacker News

astrangeyesterday at 8:29 AM1 replyview on HN

No, I'm talking about window buffers. This is about memory not disk space.


Replies

tavavexyesterday at 9:19 PM

I was talking about RAM - in that running Chromium on its own already has a preset RAM penalty due to how complicated it must be.

But window buffers are usually in VRAM, not regular RAM, right? And I assume that their size would be relatively fixed in system and depend on your resolution (though I don't know precisely how they work). I would think that the total memory taken up by window buffers would be relatively constant and unchanging no matter what you have open - everything else is overhead that any given program ordered, which is what we're concerned about.

show 1 reply