August 31, 2011

Fixing Safari on PC Woes: webkit2webprocess.exe, applemobiledeviceservice.exe

If you are experiencing Safari on PC woes – Safari does not start, Safari does not close, Safari hogs the cpu – then keep reading for possible workarounds.
 

10/17/11 Update: Safari 5.1.1 has not fixed these issues.

It is a pleasure to use Safari on iOS devices or Macs – it is fast and secure. Compared to that, Safari on PC consistently gives a bad experience – it is slow and hogs the CPU. With Safari 5.1 the experience has gotten worse.

It you have upgraded to Safari 5.1, you will see these processes running
  1. Safari.exe
And these new processes
  1. WebKit2WebProcess.exe
  2. AppleMobileDeviceService.exe
  3. AppleMobileDeviceHelper.exe while using iTunes.
The various Safari on PC woes -

Safari does not start
It is most likely because Safari.exe and WebKit2WebProcess.exe did not terminate and continue running after closing Safari in a previous session. Kill Safari.exe to fix this.

Safari does not close
While Safari windows will close, the related processes may keep running. Follow the steps above to kill the process.

Safari hogs the CPU
Safari has typically been a heavy user of CPU. Things have become slightly better with Safari 5.1 but it still consumes a good amount of CPU.

Try the following to see what is causing it,
at Edit > Preferences > Security - disable plugins, java, and javascript one at a time and see which one improves the performance. Adobe Flash plugin can be the source for excessive CPU consumption.

iPhone, iPad, iPod touch not recognized in iTunes
It is most likely because AppleMobileDeviceService.exe (AMDS) is not running. Restart Apple Mobile Device Service or configure AMDS properly as shown in the above link.



For more similar issues with Safari 5.1, check Apple support discussions here, here and here.

If you are still facing Safari issues, switch to Google Chrome – the best browser for PC’s.