4 ms·
> doesn't clog up my memory the way Chrome What exactly is "clogging up memory" that everyone here complains about? I can understand if Chrome is using 6 / 8
by Zombieball 12y ago
> doesn't clog up my memory the way Chrome
What exactly is "clogging up memory" that everyone here complains about? I can understand if Chrome is using 6 / 8gb of your ram and you are simultaneously running photoshop and it can't grab any memory due to Chrome, but is this the case?
Shouldn't Chrome use as much RAM as it can to ensure speedy performance provided its not starving out any other applications?
I have little experience in writing desktop applications & memory management in an environment of this nature. Genuinely curious what the normal practice is.
Edit: To clarify, I am assuming the memory growth is not due to any sort of leaks :)
- Outofthebot 12y agoSuperfluous RAM use hurts battery life a lot. Using Safari over Chrome easily saves 2+ hours for me.
- inclemnet 12y ago> Superfluous RAM use hurts battery life a lot Do you have a reference for why this should be? A quick search yields results suggesting only the opposite (for instance, https://superuser.com/questions/738848/does-more-ram-usage-cause-more-battery-usage https://superuser.com/questions/738848/does-more-ram-usage-c...).
- mitchty 12y agoMore ram in use generally means more javascript crap running. Which means higher cpu/energy use. Its not the memory use its what is using the memory.
- inclemnet 12y agoSo...the claim is that chrome runs a lot more javascript than safari?
- mitchty 12y agoI'll phrase it more that I see significantly more memory use in Chrome for long lived processes than I do with Safari. That said, eventually both get to 6g of ram in use and a restart is needed anyway.
- mitchty 12y agoI'll phrase it more that I see significantly more memory use in Chrome for long lived processes than I do with Safari. That said, eventually both get to 6g of ram in use and a restart is needed anyway.
- Zombieball 12y agoAh could point! I could even imagine scenarios about pre-fecthing content (say loading the next page that may never be viewed) and throwing it in RAM. Definitely would not be good for battery life. Cheers!