Mini-Tutorial: The dreaded spinning pinwheel; Avoiding unresponsiveness/slow-downs in Mac OS X
Patience may be a virtue, but in the case of Mac OS X's dreaded spinning pinwheel process indicator, even the most tranquil users can find themselves more than a tad anxious for the standard arrow cursor to re-appear and normal system operation to appear.
While virtually all users will experience a spinning pinwheel (and associated unresponsiveness from a specific application, a group of applications or the entire system) from time to time, there are a number of measures you can take to lessen the occurrence of these incidents and eliminate standstills.
Add more RAM The primary cause for overall slowness in Mac OS X and unresponsiveness from applications is a lack of adequate memory. For most users, 512 MB is the amount of RAM at which most unresponsiveness and spinning-wheel sessions dissipate. In other words, 384 MB of RAM may leave you in a lurch, while 640 MB of RAM won't provide a huge speed increase over 512 MB.
As an application uses up available RAM, Mac OS X's virtual memory system allocates swap file space on the root file system (your startup disk) for use by the application. With too little physical RAM, this swapping will occur more frequently resulting in two consequences:
- Since all mass storage devices (hard drives, flash memory, etc.) are significantly slower at moving data in and out than physical RAM, applications will suffer a significant speed hit and stall more often.
- Your startup drive will be more occupied with providing virtual memory services to Mac OS X than performing its normal functions (reading/writing files), resulting in slower disk activity and overall lackluster performance. This is also referred to as "disk thrashing."
If you are buying a new Mac, make sure it is equipped with at least 512 MB from the factory, or purchase additional memory modules from a trusted vendor and install them once your system arrives. If you're currently running a Mac OS X system with less than 512 MB of RAM and experiencing frequent slow-downs, consider adding more memory.
Make sure you have enough free space on your startup volume Mac OS X requires at least 10 percent of the volume it is contained on as free space in order to maintain the integrity of the file system. However, even with 10 percent free space, Mac OS X's use swap files - as well as extra data generated by third-party application caches, etc. - can quickly put you back into a position of possible directory/file damage and increased incidence of spinning pinwheels.
Realistically, 20 percent of your Mac OS X startup volume should be kept clear in order to achieve best performance and avoid disk problems.
Delete problematic .plist files Mac OS X uses .plist (preference) files to store various information about applications. Applications routinely interact with their respective .plist files, and when these small dockets become corrupt, individual programs may be more prone to the spinning pinwheel.
If you are having these slow-down issues with a specific application, try deleting its .plist file. It will generally be located in the ~/Library/Preferences folder, and labeled as follows:
com.(name of developer).(name of product).plist [For instance, com.adobe.Reader7.0.plist for Adobe Reader 7.0].
Simply drag the potentially offending .plist file to the trash, re-launch the hampered application, and check for continuation of problems. In some cases, applications will have several .plist files, so make sure you check for any that contain the product name. Also, note that you may lose some settings or other personal data used by specific applications when these files are deleted.
Alternatively, if you're not sure which application is slowing down your Mac or you'd like to check for any existing, but unnoticeable issues, there is a freeware utility called "Preferential Treatment" that will check for some elements of .plist file corruption.
Limiting the number of open applications If you aren't able to purchase additional memory, or if your system continues to experience routine slow-downs despite the presence of adequate RAM, try limiting the number of open applications.
Every open application, even if it is not performing any noticeable tasks, uses a portion of the Mac OS X virtual memory block. Closing unnecessary or infrequently used applications can therefore result in a reduction of spinning-wheel episodes.
More uptime, more stalls: Restart more often Although Mac OS X was designed to run 24 hours a day without a restart and does so well in most cases, some user set-ups may -- for varying reasons -- benefit from more frequent restarts.
Dealing with most notorious culprit: Safari The application implicated in far more spinning-wheel stall instances than any other is Apple's own Safari. Since Safari is tied to so many critical and shared components of Mac OS X -- the WebKit, Java, QuickTime, etc. -- this is somewhat expected. That said, there are a few workarounds that can lessen this behavior.
Disable AutoFill forms A number of user cases have shown that disabling the automatic form filling feature in Safari's preferences can dramatically reduce the number of stalls. In order to do this, open the preferences pane in the "Safari" menu, click on "AutoFill" and de-select all of the available options.
Use keyboard shortcuts instead of mouse clicks For reasons unknown, Safari is sometimes more prone to stalls when mouse clicks are used to perform actions like closing windows or moving to different text boxes on Web forms. Using keyboard shortcuts instead (Command-W to close a window, or the tab key to move between form fields) has been shown to avoid this particular type of problem.
Perform an Archive and Install process As a last resort, performing an Archive and Install process will sometimes eliminate inexplicable stalls that may be due to file corruption.
The process will remove all of your current Mac OS X version's vital (and potentially problem-causing) components, and replace them with the components of a fresh copy provided by the Mac OS X disc that shipped with your system, or a retail Mac OS X disc. Unfortunately, this means you will lose some system settings and some or all third-party system add-ons.
To begin the process, insert your Mac OS X CD or DVD, as indicated above. Restart your machine and hold down the "C" key to boot from the newly inserted disc. Follow the on-screen instructions, and after accepting the license agreement, click "Options." Select "Archive and Install," and check the "Preserve User and Network Settings" option if you'd like to do so.
After the installation process is complete, you will be left with an earlier version of Mac OS X. However, you will likely want to bring your installation back up to the current version of Mac OS X.
Various updates, back through Mac OS X Combo Update 10.2.5, are available from Apple's Support Download page.
Restore your settings and appropriate third-party software, and you will find your system with approximately the same status as prior to the Archive and Install
Your old system will be stored in folder called "Previous Systems" at the root level of your startup volume. If you would later like to delete this folder, you may need to change its permissions.
Like what you've found in this tutorial? Get more troubleshooting guidance (updated daily) by subscribing to MacFixIt Pro.
Resources
one office and one in the studio. The studio one has slowed to a crawl, and
the office one is fine. Tons of ram in both. I will follow advice on this page
and post my results.
Well it's been over 2 years dude. What were your results?
appropriate third-party software", sounds prohibitively difficult. Does it really
mean that you have to reinstall all software products and updates that are not
part of OS X?
Not at all: I did that a week ago, and I could hardly tell a difference. The only
changes were that a couple of dock icons were replaced with question marks,
and some drivers had to be reinstalled. I guess that's what's meant by "3rd party
add-ons". I had no choice in the matter, because the upgrade install just
wouldn't run, but the Archive install has worked out very smoothly.
It's not easy if you have more than one account! The AppleCare guy had my
sister do it, and was of course she was completely stymied as to how to get
the rest of the families accounts working, as well as to access some
directories now lacking permission to. I had a special set up so the buys
could share the iTunes library too. She gave up and shipped mer her ibook.
Since I had to redo the whole thing for her, I talked her into buying Tiger.
Thank goodness for unix - learn how to use chown and chgrp commands just
in case.
I'll second that. I do this sort of thing professionally and, although OS X is steadily getting better for administration from the GUI, I often seem to get to a point where I have to use the UNIX command line to get these things to work.
I had disconnected my radioSHARK and Wacom Tablet, but I noticed that the radioSHARKServer, TabletDriver and InkServer were all still running. I killed them all with no ill effect (I didn't notice any positive effect either).
But what about the other ones? Are multiple copies needed?
Here's a great assignment for MacFixIt:
Create a reference of the processes that run in OS X. At least the ones used by Apple since third-party processes are usually self-explanatory. This reference would include a brief description of each process' function, what the appearance of multiple copies means, what the consequence of killing the process is, what normal running parameters (CPU %, real and virtual RAM) are and under what conditions should you consider kiiling an out of control process.
This would be great information and would be a worthy resource in the tradition of the MacFixIt site.
Oh, you're welcome for the brilliant idea -- I got a million of 'em.
I agree that this would be very useful. There are several such references for this purpose in the PC world, enabling killing of unnecessary processes and also prevention of auto launch at startup. By referring to such online info I have been able to dramatically increase the performance of several PCs. So an equivalent in the Mac world would be great.
Thanks for if/when it is developed.
your mac, restart and press cmmd-s when you hear the start up chime.
keep holding until you see white on black gobbeldy **** scrolling down. at
the end of the line type in fsck -y, hit return.
if at the end of the run it says file was modified, then run it again untill you
get an 'ok'.
type reboot, the mac will boot as before. this works everytime and my
recommendation is that this shoudl be done as a routine maintenance.
Well, I run fsck -fy (Journaled HFS+) almost on a daily basis because Safari
has been slowed down by the dreaded spinning rainbow ball beyond my
tolerance! And, it has done nothng for whatever mischief Safari has wrought
on my OS X 10.3.9 otherwise very sweet running system.
And, I am obsessed with running maintenance because I am an intermediate
beginner with a lot of curiousity and I love to download stuff to see what
happens when I push enter ...
Knowing I am not yet at the point where I keep a sweet system paired to the
basics, I run Yasu, Disk Utility, Tech Tool Pro, chrons, prebinding, Cocktail,
Mac Janitor, Permissions Doctor, Preferential Treatment, Cache Out X,
Cronathon 1.6, Macaroni, Mac Sweeper and DeLocalizer, as well as I am
slowly moving into CLI manipulations i.e.
< applejack auto restart|shutdown >
What reduced the occurence to once or twice a day was a little app, Bookdog,
that removed a reported 2,000 duplicate Bookmarks, and organized the
remaining Bookmarks. That seems to have made all the difference.
/dd
http://docs.info.apple.com/article.html?artnum=106214
They say 'an Apple a day keeps the beachball away'
in this case, they mean using APPLEJACK-(via Versiontracker X)
its a short process I do every morning at startup-and problems are few and far between...
inadvertently clicked on aliases that are attached to files on volumes that no
longer exist or are no longer share points. Doing so will initiate a two-minute
pinwheel, as the Finder fruitlessly searches the network for the missing
volume. Very frustrating. Clean up those obsolete aliases, but do it in list or
icon view.
- if the red and yellow part take up almost the whole circle, you are absolutely at the limit (for me the red and yellow part is usually around between 400 and 700 MB).
- if you often have more than let's say 15% in green, you are not really using your Mac to it's full potential, just keep a few more apps open in the Dock, there is no need to quit them (if the are not processor hogs like Word)
About low disk space:
- check the sum of all files in /var/vm (2 GB in my case), your free disk space should be always higher than it. If you want to burn CDs or DVDs, you should add the ~700 MB or 4.2 GB to that number.
But what is the blue part about, ie 'inactive'? What does that mean?
cause or contribute to the spinning pizza wheel. It eats up 5-45%
of CPU time, 38MB of real memory, 1.14GB of virtual, and 31MB of
shared memory. Its parent process is WindowServer, it has 14 threads and
232 ports, CPU time since I restarted 2 days ago is 53:42, 44790482 context
switches, 27513 faults, 1970 pageins, and gazillions of Mach Messages In/
Out and Mach/Unix System Calls. What the hell is this? Is it a virus or worm?
I can't quit it, I have to force-quit it from Activity Monitor; nothing bad seems
to happen, but it comes back after a while. Weird! What is it???
---
Gib Henry
I've been in IT for more than 15 years, I administer UNIX and Linux based Servers, we also have Macs and PCs in the office and I've used Apples since my ][e Pro. I also run Linux on both Macs and PC's at home along with OS X on a few of my old and new Macs. I've used OS X since the Beta 10.0.
I want to know exactly WHY Apple continues to allow (or maybe they created it) this "dreaded spinning pinwheel" of death to perpetuate through FOUR GENERATIONS of OS X, and it seems that it's only far gotten worse in Jaguar and Panther?!
This problem DOES NOT exist on any Mac I've installed Linux on and it certainly doesn't happen with UNIX, even installed on a plain-ol x86 based desktop! (First off, ANY UNIX admin knows you always create a "swap partition #1" on ANY UNIX install, something I also do for Linux installs). Why hasn't Apple endorsed this, if OS X is so UNIX based? Apple even stupidly put OS 9 on the same partition as OS X on new computers till recently! I always separated them on office Macs and on my Macs at home.
I don't "buy" the 512MB RAM solution either. As a test a while back, my YDL 2.0 and 3.0 (Yellow Dog Linux) installs ran happily on as little as 128MB and great with 256MB on a G3 350 and G4 400 Power Mac! If 512MB is so necessary, WHY is Apple only putting 256MB of RAM (128MB until recently) in most new G4 and G5's ??? (Although I suspect greed is part of the reason). I have a G4 Dual 1.42GHz PM with 2GB of RAM ... and I still get the "dreaded spinning pinwheel" of death.
I'm not a "coder", only an IT Admin, so I can't tear apart OS X to the guts, but I do know Linux and UNIX, and I postulate that OS X is a poorly written version of UNIX with too much fluff, not enough headroom and poor coding. We've certainly seen the "brilliant" job Apple has done on some botched updates.
OS X 10.0 was purer, but had bugs. OS X 10.1.5 was very clean and VERY speedy compared to snail slow 10.2 and 10.3. I never had a serious problem with 10.1.5 and it's too bad Apple went down the wrong path with 10.2 and up.
Personally, I'll take Yellow Dog Linux over OS X anyday, except that there just aren't the Apps that X has .... too bad. So I still ask, looking for a few legitimate reasons, "why has Apple let this problem perpetuate?"
Course it's still better than all the Viruses, Trojans and Spyware on Windoze.
- by robogobo March 13, 2005 9:02 PM PST
- <class="merchant"><span>></span><div class="datestamp"><i>This is a reply to a previous comment by CounterPoint</i></div></class><br />
- Like this Reply to this comment
-
Showing 1 of 2 pages (40 Comments)Ok, take a deep breath....
First, it's not the Pinwheel "of Death". The Pinwheel is there to indicate a catch-up time necessary to continue heavy processing, or to resolve a conflict of RAM allocation, Cache, or something else that needs time to complete. In rare cases, these things cannot be reolved. But most often, you wait a bit and it's done. This tutorial was created to help that happen less frequently.
Linux, Unix, Windows, and OS X all experience hangs from time to time. The pinwheel is just an indicator. Yes, Apple invented it. And it only gets "worse" when you upgrade an operating system because your machine gets relatively slower than the newer machines the OS is designed for.
So take a deep breath, count to ten, or twenty, and the small death should be over. cheers.