Our use of Parallels on Macs is limited to a single task that requires four applications to be open in Windows: IE6, Thunderbird, Word 2003, and ImageNow (a document imaging app).
Two days ago, as part of regular maintenance, we upgraded one user from OS X 10.4.9 to 10.4.11, applied other Apple system and security updates, and updated to the current version of Parallels from build 4560.
Subsequently, this user has seen Parallels quit unexpectedly and repeatedly, and is seeing extremely slow performance in the Mac OS. She reports that both the crashing and the slow Mac performance seem connected to the use of IE in the virtual environment: Until IE is launched, performance is normal. After IE is launched, she can restore normal performance only by logging out of Windows.
It appears IE6 may be triggering something in Parallels and/or Windows that causes Parallels to crash, and bogs down the Mac OS. Significantly, Mac performance doesn't improve after a Parallels crash - only when the user is successful at logging out of Windows.
We've never seen similar behavior before, and we're baffled about how to fix it. Suggestions would be appreciated.
- John Norris, Academic Advising, Duke University
Two days ago, as part of regular maintenance, we upgraded one user from OS X 10.4.9 to 10.4.11, applied other Apple system and security updates, and updated to the current version of Parallels from build 4560.
Subsequently, this user has seen Parallels quit unexpectedly and repeatedly, and is seeing extremely slow performance in the Mac OS. She reports that both the crashing and the slow Mac performance seem connected to the use of IE in the virtual environment: Until IE is launched, performance is normal. After IE is launched, she can restore normal performance only by logging out of Windows.
It appears IE6 may be triggering something in Parallels and/or Windows that causes Parallels to crash, and bogs down the Mac OS. Significantly, Mac performance doesn't improve after a Parallels crash - only when the user is successful at logging out of Windows.
We've never seen similar behavior before, and we're baffled about how to fix it. Suggestions would be appreciated.
- John Norris, Academic Advising, Duke University