Slashdot Mirror
Google Chrome 55 May Use Less Memory (blogspot.com)
Slashdot reader justthinkit writes: Google Chrome is arguably the best browser and the biggest memory hog. Presently. But the Google engineers are hard at work, optimizing the next version of Chrome. Will this be an important, or just another incremental, upgrade?
They're specifically targeting the browser's JavaScript engine, V8, and they've already "analyzed and significantly reduced the memory footprint of several websites that were identified as representative..." (For example, on the mobile New York Times site they've reduced heap memory consumption by about 66%.) Chrome 55 is scheduled for release in December. Any Chrome fans looking forward to testing its performance?
They're specifically targeting the browser's JavaScript engine, V8, and they've already "analyzed and significantly reduced the memory footprint of several websites that were identified as representative..." (For example, on the mobile New York Times site they've reduced heap memory consumption by about 66%.) Chrome 55 is scheduled for release in December. Any Chrome fans looking forward to testing its performance?
it may not
"We used the tool to identify inefficiencies with a number of internal types." That is about the most technically interesting part of the whole article. Would have been nice to have a bit more of what was changed, how, why, ...
... on linux, then I won't be using it on Linux and would recommend others don't either. Google may think its sandbox code is perfect with no possible exploits but I don't intend to test out the veracity of their naive belief for them on my systems.
Needing root access would mean needing to sudo to run chrome, correct? I don't know what you're doing, but my chrome processes run as user processes, not root processes
Google Chrome 55 May Use Less Memory
But then again Kate Upton may come by my house tonight looking for a good time. I figure the probability of both being about equal.