🙂 Thank you again for your experimentation, Wickham.
So if there is an interaction, it's not something that we can easily check on using Task Manager to just check on the processes.
There was a hint in a different thread yesterday that such interactions could be happening on a very low level indeed with Safari. I was working with SexyGeeky on an odd launch freeze/hang. We'd narrowed it down to a user-account-specific issue, probably related to the preference files. And in the course of swapping out individual plist files, we provoked a "Safari has encountered an error message". On further investigation, the faulting module turned out to be
ntdll.dll:
http://discussions.apple.com/thread.jspa?threadID=2265392
... which is about as fundamental a dll as you can get on the XP OS (or any Windows OS). Rather startling to see ntdll.dll implicated in an error message under those circumstances. (Hence my quick check in that thread to see if Safari was still launching in the other user account for Sexy ... I was wondering if perhaps *something different* had started to go wrong for her in the middle of the troubleshoot.)
Unfortunately, there's a sense in which the possibility that some effect could ramify through ntdll.dll to Safari *opens up the field a bit much* for us. That dll is fundamental enough that the interaction could be related to:
drivers
hardware devices
software devices
cabling and connections
OS components
disk damage
Perhaps the folks running Process Monitor (in this thread) might be able to give us a heads up on whether it is possible to track performance of such items at the same time as watching the CPU behavior (and drive behavior) on the affected systems while Safari is running.