Don't be too sure of that yet Ianxxx. I thought the same for a while, but...
Last night, I turned Little Snitch off (to rule it out) and I was running Transmission to download a couple of torrents. I added an XVid torrent and started downloading it to my desktop. I looked over at my Console and suddenly, I noticed that "quicklook" (the process that creates thumbnails for files) was trying to create a thumbnail for the XVid movie. The thumbnailing process failed (probably because the file wasn't done downloading yet), and it was rapidly spitting out this same error message over and over again:
Code:
3/20/08 2:06:44 AM quicklookd[1193] [QL ERROR] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/agrafuese/Desktop/xxxyyyzzz.avi>'
3/20/08 2:07:35 AM kernel CODE SIGNING: cs_invalid_page: p=1206[lssave] clearing CS_VALID
It repeated this about a thousand times (not exaggerating), and the "p=" part of that second line grew higher and higher in number.
Now, I know why this happened: it is because Finder tries to create thumbnails for any file that is in an "active" window. Since the desktop is technically a constantly "active" window, it wouldn't stop trying to create the thumbnail as it failed each time. So, because this error was repeating and Finder was trying soooo hard to make it happen, my system bogged down A LOT, and lo and behold: The return of the jerky mouse! I eventually stopped downloading the file, moved it to a folder that wouldn't be in an "active" window, and the errors in Console stopped. However, the jerky mouse remained. It appears that when Leopard gets stressed, it doesn't recover after the stressful incident has stopped. It doesn't "refresh" itself in any way, apparently.
Now, this thumbnail scenario is very rare, and I know it is not THE ONLY reason that a jerky mouse will occur. BUT, I believe the answer lies in this following statement:
The mouse, GUI, and performance problems will occur when the system is under large amounts of stress of
any kind. Period. There is no ONE solution, and it is not always related to the internet or networking. It could be anything: an intensive process, a power-hungry app, too much file-processing, repetitive errors (in my case), and on and on and on.
So what do we do about it? Well, if I am correct, there is nothing that can be done. We don't know if Zeph can do anything, because this may be a genuine Apple bug straight from the developers' desks. All we can do is keep Zeph notified and hope he chooses to help us out in any way he can.
Well guys, that's my 2 cents. I could be wrong, and I hope I am, but I have a feeling I'm not. Good luck to us all.