2

I have two iMacs and just installed OS X Lion (clean install) on one of them (let's call it iMac A). I did a Time Machine backup and restored that backup to my other iMac (B) to avoid installing twice. Everything works perfectly except that Google Chrome is extremely slow on iMac B (where the Time Machine backup was restored to). Opening a new tab is slow, opening a web page is slow etc. Safari on B is fast and works as it does on A, so it's just on B that Chrome is slow (and Chrome is my preferred browser, so I'd like to get it up to speed).

To solve the problem on B, I've tried uninstalling Chrome (see How do I uninstall Google Chrome *completely* from my Mac?) but uninstalling and reinstalling did not do the trick.

Does anyone have an idea why it is slow only on B and how to fix it?

Community
  • 1
rassom
  • 903

2 Answers2

1

Weird issue indeed. Have you tried to use Chromium to see if the issue is the same? I'm interested to see if the slowness persists using a slightly different flavor of the browser. If the slowness still persists, we know its likely a problem with the shared resources/files the browsers use.

Let me know

Tyler Miranda
  • 151
1

I've now installed first OS X Lion from scratch, then installed Google Chrome - and Chrome performance is good again. Weird that it requires a complete OS re-install to fix the performance of Chrome!

UPDATE 22 September. I have now received the solution below from Parallels support and have confirmed that it works (i.e. restores performance of Google Chrome):

  1. Please go to /Library/Preferences/Parallels
  2. Locate network.desktop.xml file. Make a backup copy of it to Desktop.

  3. Open the file and locate the following string:

    <ParallelsNetworkConfig schemaVersion="1.0" dyn_lists="VirtualNetworks 1 VZNetworkConfig 0">
<SystemFlags></SystemFlags>
<IPv6Enabled>1</IPv6Enabled>
<VirtualNetworks id="0" dyn_lists="VirtualNetwork 12">

  4. Change the value in IPv6Enabled to 0 (1 => 0)

  5. Save changes and close the file.

  6. Quit Parallels Desktop if it is running.

  7. Open Terminal and issue these commands:

    sudo launchctl stop com.parallels.desktop.launchdaemon

wait for 10 seconds, then this commmand (still in terminal):

sudo launchctl start com.parallels.desktop.launchdaemon
  1. Start Parallels Desktop, go to the Virtual machine Configuration - Hardware and change the Network Mode to 'Bridged'
  2. Check if the issue persists.
rassom
  • 903