Another upgrade, beach ball still here!
Can someone please explain what causes the ?Spinney Ball of Death?? It always comes at the most inopportune times. Is this on anybody?s programming Queue to fix? I see updates after updates for OSX but I never see this problem being address. You guys on this board must notice this as a problem, or am I the only one who apparently stresses out his computer by playing a QuickTime movie and surfing at the same time. I was hoping by purchasing a 1ghz Powerbook with 1gig of memory and an upgraded HD to 5400rpm would be sufficed. Don?t get me wrong the computer seems fast enough, however this beach ball needs to be deflated, cause it?s making me batty.
Comments
<strong>Why isn?t there an auto kill, CPU talking, ?I see this program is not allowing the user to do anything I better kill what?s ailing me?.</strong><hr></blockquote>
A single-thread application won't let you even click the menu bar when it's busy. Sometimes it's normal (heavy calculations), sometimes it's bad design (Finder often halts on CD insert/eject). Anyway autokill might erroneously kill a process which is simply very busy.
[quote]<strong>If Sun, IBM or HP had this problem their UNIX business would be none existent.</strong><hr></blockquote>
OS X is still young and a great dead weight of legacy stuff is holding it back. One fine day we won't have these problems.
[quote]<strong>Maybe this bug will be fixed when Apple goes to 64 bits.</strong><hr></blockquote>
64-bit support has nothing to do with task scheduling, one-threadedness and developers' lazyness.
And fix these question marks already! <img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
[ 02-21-2003: Message edited by: RodUK ]</p>
<strong>If Sun, IBM or HP had this problem their UNIX business would be none existent. Maybe this bug will be fixed when Apple goes to 64 bits. Here?s hoping sooner then later.</strong><hr></blockquote>
It's not a bug. As others have said, it's an indication that an app has been busy for over (I think) 2 seconds.
I'm inclined to say that you're trolling because most people don't have trouble with the SBOD on way slower systems than yours. Maybe you need to start from scratch on your system. Something sounds wrong, either with your intentions or your installation.
The spinning disc cursor is not a system-wide problem. When it pops up it only affects the single stalled application (almost always). In fact, you can actually see this when you move the cursor around the screen. Take this example. Here we have Finder and iTunes in the background with QuickTime Player in the front.
Let's say QuickTime Player freezes up for some reason and you get the spinning cursor. Only when the cursor is over QTP's windows will it be the spinning cursor. Specifically, only over the yellow area seen here:
If you switch to another available app, you can work just fine as if there's no problem at all. In this example, I switch to OmniWeb here. Now, QuickTime Player is still stuck in the background, but I can go about working in my other apps just fine. When I move the cursor over the background window (note the yellow again), I'd see the spinning disc again, indicating that the app it's over is still not responding to system events.
I think it's very important to make this distinction here because before I pointed this out, some of my colleagues thought that they just had to sit and wait when that cursor popped up. Not true for good multitaskers!
[ 02-21-2003: Message edited by: Brad ]</p>