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.

Lion - Safari 5.1 - Webprocess

Webprocess - consumes 80 to 90 % of CPU utilisation n Lion.


This is observed for all pages which are graphic intensives. For normal web pages it takes aroung 15 to 20 % of Cpu

utilisation.


Macbook pro 17" with i5 and 8 gig of ram.


Any one observed this and any solution to this problem.

Posted on Jul 23, 2011 3:38 PM

Reply
17 replies

Jul 28, 2011 7:12 AM in response to Taurus_Bull

Safari 5.1 and “WebProcess”: PROBLEM SOLVED

The culprit is “Little Snitch”


I am running OS 10.6.8 (Lion-ready). Yesterday, I installed the Safari updater from 5.0.5 to 5.1 . . . and am experiencing repeated and annoying pop-up windows for "WebProcessing."

I found the culprit to be the third-party utility "Little Snitch" — which monitors outgoing internet connections. (http://www.obdev.at/products/littlesnitch/index.html).

I solved the problem by upgrading (FREE) Little Snitch v2.0.x to v2.4 (for Snow Leopard and Lion).

PROBLEM SOLVED.

Aug 23, 2011 8:14 AM in response to Taurus_Bull

@Kisuke3


You wrote:
"Add a new rule, name it "WebProcess" and in the port put in there 80 add a new rule again, name it "WebProcess" and in the port put in there 443."


It might be helpful to those less knowledgeable if you specify the navigation route you used to add the new rules. Likely, this is unfamiliar territory for some.


HERE IS SOME ADDITIONAL INFO that might help with this issue of Safari 5.1 and Lion:


In another Apple Discussion [https://discussions.apple.com/thread/3193055?start=15&tstart=0 -- "Safari 5.1 not working on 10.6.8"] here is a comment originally posted by Brett Stewart, and then slightly amended by me. Although it is directed at OS 10.6.8, it might also apply to OS 10.7:


Brett, your solution worked fine for me, too. THANK YOU!


However, for those who might wish to follow your navigation route, I found it to be correct right up to the name of the app.


Maybe it used to be named "WebProcess.app" . . . but in my OS 10.6.8 it is named "PluginProcess.app".
"PluginProcess.app" is the app that's in the "WebKit2.framework" folder.


So, the navigation route is:


Go to System Prefs/Security/Firewall/ Advanced.

Click the plus button to add an allowed process to the firewall.

Navigate to the PluginProcess.app (boot/system/library/Privateframeworks/WebKit2.framework/PluginProcess.app)

Add this to the firewall's allowed processes.


According to the above, the app in question -- on your computer -- might be named "WebProcess.app" or it might be named "PluginProcess.app." In either case, follow the navigation route shown above, and "Allow" it.
I haven't, as yet, upgraded to 10.7; still using 10.6.8. However, like I said, the above information might be relevant for Safari 5.1 on OS 10.7 as well as on 10.6.8.


--David Purnell

Sep 22, 2011 9:36 AM in response to David_Purnell

David_Purnell wrote:


Safari 5.1 and “WebProcess”: PROBLEM SOLVED

The culprit is “Little Snitch”


I am running OS 10.6.8 (Lion-ready). Yesterday, I installed the Safari updater from 5.0.5 to 5.1 . . . and am experiencing repeated and annoying pop-up windows for "WebProcessing."

I found the culprit to be the third-party utility "Little Snitch" — which monitors outgoing internet connections. (http://www.obdev.at/products/littlesnitch/index.html).

I solved the problem by upgrading (FREE) Little Snitch v2.0.x to v2.4 (for Snow Leopard and Lion).

PROBLEM SOLVED.

The problem is not Little Snitch as this occurs without Little Snitch.

What you thought fixed it is restarting the system and a new browser session.


This is the same old problem with Safari going back several versions, where it just keeps an ever growing cache / leaking memory until you run out of RAM and start having lots of page-outs and see Safari being less and less responsive. WIth or without the beach ball.


The only difference now is that Apple separated WebProcess off from Safari.


You now no longer have to force-quit Safari, you can just kill WebProcess and your tabs etc remain open, and can continue browsing without losing where you left off.


Once you start a new session, everything is back to normal, but just wait a number of hours or days, depending on how active you are online and see WebProcess grow uncontrollably.

Lion - Safari 5.1 - Webprocess

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