You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Web Process + Safari now hogging 50-75% more memory than Safari 5.0.5 did

Now that Apple has split Safari into two processes — Web Process (handles page loads and other traffic) and Safari (handles interface, bookmarks, history, etc) — these two processes together are using 50% to 75% more memory than Safari did before the upgrade to 5.1.


Three days ago, the most RAM I'd ever seen Safari hog (after several hours of surfing multiple tabs) was 1.1GB (still way more than it needed, once back down to 3 or 4 tabs).


Today, after surfing only an hour:


WebProcess 1.3GB

Safari 552MB


Anyone else seeing this? And anyone have ideas about limiting this memory hogging?

Macbook Pro 13, Mac OS X (10.6.4), 10.6.7

Posted on Jul 27, 2011 2:04 AM

Reply
72 replies

Oct 19, 2011 6:36 AM in response to 100 Watt Walrus

5.1.1 has NOT solved the problem. Safari still eats too much RAM and drastically slows the whole computer down. This Safari issue has highlighted another problem with OS X Snow Leopard that Apple never seems to have fixed - Snow Leopard will start writing to disk when free memory runs low inspite of having over 500 MB of Inactive Memory available. When free memory runs low the OS should ideally free up inactive memory or allocate it to other processes that need it, but it doesn't seem to be doing this at all, at least not very efficiently.


I'm not sure whether to move to firefox permanently or add more RAM to my mac - I miss Steve!! 😟

Oct 21, 2011 10:28 AM in response to Andrei P.

I learned about the Sunspider benchmark from around these communities, and running it it very quickly and clearly demonstrates that there is some major problem with extensions.


And I don't think it is the extensions' fault. How could it be if running a completely unrelated set of javascript tests (Sunspider) causes memory to be devoured?


With extensions turned off, Sunspider runs in seconds and Safari's memory usage is nominal.


I think the problem is in Safari's extension implementation and not in the extensions themselves. I also do not have Flash installed, and perhaps there are problems in plugins as well.


With sadness, I switched to Chrome. I miss Safari's Reader feature most.

Oct 30, 2011 5:24 AM in response to CFnyc

CFnyc, you're right! Thanks for the tip.


Turning off extensions completely from Safari (5.1.1) preferences seems to have solved the problem. Safari as a whole (including WebProcess) rarely, if ever, uses over 400 MB of RAM. I've had extensions turned off for about a week now and the sluggish performance issues have disappeared. Turn extensions back on and Safari returns to its old behaviour.


I do miss certain extensions though - especially, AdBlock.

Nov 4, 2011 10:58 AM in response to rahul.l

It's ridiculous that we must disable all extensions just to have it run somewhat ok! I sure wish Apple simply FIXED Safari, so that it works, and can make use of the extensions always touted by Apple as a means to "customize" our experience!


I'm still using 5.0.5 after going thru an awful month of 5.1, and will not try again until I am certain they've de-bugged it, and get Autofill back to working the way it should. Yes 5.0.5 still will creep up to even 2GB of RAM usage, but I have dozens of windows/tabs open at a time, so I expect higher numbers, but with 5.1 it was a total mess, higher usage, slowing things to a crawl, glitches & crashes, & well, it was horrible.

Nov 11, 2011 6:35 AM in response to jfaughnan

Safari's fall has forced me to genuinely evaluate both Chrome and Firefox. There is simply no comparison. Firefox is more 'akin' to Safari. Firefox looks like Safari. Firefox is stable. Firefox is insanely fast at loading pages. In Firefox, pages don't flicker as they are loaded or switched to. Firefox handles large number of tabs like a champ. I am so pleasantly surprised by its capabilities that I finally don't even feel the need to look back. I wrote a review of Chrome earlier in this thread. As a Safari user, I was simply dissatisfied with my Chrome experience. Hope this is helpful.

Mar 24, 2012 3:05 PM in response to 100 Watt Walrus

Sadly, I have this issue now. My MacBook Pro is 1 1/2 years old. I upgraded to Lion last fall. About a week ago Safari started running very slowly, and my MacBook was heating up. Running top -o cpu showed that WebProcess is consuming up to 100% of Ram. Don't really want to use Chrome, but Safari is now unusable. I'm shocked that this problem was reported a year ago and disappointed that Apple still hasn't fixed it yet.

Jun 19, 2012 10:17 AM in response to perefromgirona

Based on the information you all provided, I have been doing some additional testing and discovered that if you disable Javascript in Safari, the problem goes away. Give it a try.


I have switched to Chrome a few months ago, but came back to Safari because Chrome has serious memory leaks.

In Safari's case, it seems to release to the system all the memory it used whenever you close it.


Also, this Javascript problem doesn't happen on all websites. No problems in the MacRumors site, but if you go to the Forums of XDA Developers, you will notice how Safari Web Content grows out of proportion; and when you close Safari, it shrinks back to a reasonable size.


So the word is: Disable Javascript ion the meantime while Apple figures this out.

Jun 19, 2012 10:46 AM in response to johnfromplantation

As a side note, I am noticing that my MBP runs much cooler (133 ºF vs 156ºF) now that I have disabled Javascript in Safari.


I also compared memory usage with DNS Prefetch enabled and disabled, and there is a small difference (eats about 300MB more when enabled, but it doesn't increase the size of Safari Web Content that much).

Apr 7, 2013 8:07 AM in response to Jeremy Kinsey

I hear ya, it's pathetic, and quite sad.... I just tried using Safari again yesterday, and got so frustrated, it's back to Chrome, which I'm not in love with, but at least works better & for longer, than Safari!


Apple's really fallen down when it comes to Safari, and iTunes as well. What kind of problems are you having with Apple Mail? What do you use as an alternative? I'm not wild about using web-based mail programs as my main one...

Web Process + Safari now hogging 50-75% more memory than Safari 5.0.5 did

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.