Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

dogslobber

macrumors 601
Original poster
Oct 19, 2014
4,670
7,809
Apple Campus, Cupertino CA
Chrome uses 5x the memory on Sierra as it does on Windows 10. Why is Sierra such a memory hog where Windows 10 is lean and efficient? Time for you to streamline the OS, Apple. It's good for the environment.

(Posted from Windows 10)
 

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
Thats <obviously> a Chrome issue, not Sierra's. Apps request memory, it isn't dictated by the OS. Due to the user base size Google will put much more effort into Chrome running on Win10 than on Sierra but it is still a Chrome issue.

And <obviously> streamlining the OS will have zero effect on Google's Chrome code...
 
  • Like
Reactions: Rok73 and DeltaMac

Project Alice

macrumors 68020
Jul 13, 2008
2,079
2,160
Post Falls, ID
I don't use chrome, but I know that it has the highest ram usage of the main web browsers. Why it has become more popular than Firefox is beyond me. On Mac I use Firefox, and mainly safari. On windows 10, edge, and Firefox.
Having windows 10 installed on my Macs as well I can tell you that Sierra definitely uses less memory and runs a lot smoother. I would say your problem is using a browser that feels empty but uses 10x the amount of ram as the other options.
 
  • Like
Reactions: 0388631

0388631

Cancelled
Sep 10, 2009
9,669
10,823
I don't use chrome, but I know that it has the highest ram usage of the main web browsers. Why it has become more popular than Firefox is beyond me. On Mac I use Firefox, and mainly safari. On windows 10, edge, and Firefox.
Having windows 10 installed on my Macs as well I can tell you that Sierra definitely uses less memory and runs a lot smoother. I would say your problem is using a browser that feels empty but uses 10x the amount of ram as the other options.
Each extension, plugin in use and tab has become its own process in Chrome. With Firefox 57, it will be like this, too. If one extension, plugin or tab breaks/crashes, it doesn't bring the whole browser down with it. Currently and for a few years, Firefox boxed out plugins in use. So if they crashed, it wouldn't bring the browser as a whole down. Firefox 57 also addresses bad extension programming. Technically, a browser using more RAM is actually a good thing. It's going to be snappier. However, if the RAM available on the system is reduced to a level that hampers overall system performance, you're going to have a bad experience. Mozilla also plan on shipping out x64 as standard with FF 57 over x86 as they have for years.

Edit: I should note this on Windows. I can't speak for Sierra. Since I don't use Chrome on Sierra. However, I do recommend submitting bug or issue reports to the Chrome development channel. Every opinion and suggestion counts!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.