• On BNET: Are these ads too sexy for TV?
advertisement
Click Here
January 24, 2008 9:00 AM PST

Inexplicable slow-down? Check for hanging processes

by CNET staff

Thursday, January 24th

As we've noted a number of times, checking Activity Monitor (located in /Applications/Utilities) for stalled, processor hogging or otherwise unruly processes can be a great routine for eliminating inexplicable system slow-down (see our tutorial for information on using Activity Monitor to this end). Essentially, you're looking for processes that are displayed in red, or that are using large swaths of processor time though they aren't performing any activities.

Such an inspection recently proved fruitful for Birgit Zeiter, who discovered that the SystemUIServer process was hung.

"We just had an MacBook Pro 2.16 GHz Intel Core2 duo with 1GB Ram, System 10.4.11, with a hanging SystemUIServer."

The hung SystemUIServer was causing general system slow-down and lack of responsiveness.

Once the problematic process had been targeted, Zeiter knew where to look:

"Deleting ~/Library/Preferences/com.apple.systemuiserver.plist logging out and in again solved the problem, all menu icons in place again, the machine works fast."

But what if you're not sure where to look? The ~/Library/Preferences/ folder is a good place to start. Look for files that math or closely resemble the name of errant processes and temporarily remove them from the folder, then restart and check for alleviation of the problem. Sometimes you'll need to wait and see if the process will hang again after routine operation (it might not falter immediately after a restart).

Other good places to look for culprits include plug-in directories. For instance, a number of users have found the process UserEventAgent hanging or exhibiting inordinately high processor usage. This process is used to handle interaction with various device drivers, and as such, is prone to hangs, spikes in processor usage and other issues caused by potentially faulty devices or device drivers. In some cases, just quitting this process (using Activity Monitor) does the trick, eliminating slow-down on a semi-permanent basis. In other cases, actual drivers must be removed. A number of users have fingered audio-related plug-ins, such as those located in:

  • /Library/Audio/Plug ins/

Errant devices can also be to blame, especially if you see processes like usbmuxd hanging. Try disconnecting the devices tempoararily, forcing the aforementioned process to quit with Activity Monitor, or deleting kernel-related caches as described in this tutorial.

Feedback? Late-breakers@macfixit.com.

Resources

  • our tutorial
  • this tutorial
  • Late-breakers@macfixit.com
  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register)
    by jerroldleichter_dotmac January 24, 2008 9:05 PM PST
    I've found the same behavior, but the problem isn't really a <i>hung</i> SystemUIServer process - it's a <i>huge</i> SystemUIServer process. I've seen the thing grow to over a GB of virtual memory. (This is on a PowerPC system running 10.4.11 with 1.25GB of real memory.) When the process gets this large, your system is likely to begin thrashing - spending much of its time swapping. The effect is particularly noticeable when you switch from one user to another, but eventually everything bogs down. A huge SystemUIServer like this will look hung when it stalls waiting for its own pages to be swapped in.

    Oddly, on my system, this happens for only a single user - the SystemUIServer processes for the other users remain reasonable in size.

    It is <i>not</i> necessary to log out and in again. You can kill the SystemUIServer process using Force Quit from Activity Monitor. Mac OS will immediately create a new one for you. The new one will start out at a few 10's of MB of memory, and within a few minutes, your system should start responding normally. All your existing windows and applications will continue as if nothing happened. However, if your experience is like mine, the process will immediately start growing again. I get a couple of days of "good behavior" every time I "punish" an overgrown SystemUIServer.

    This behavior seems to have started around 10.4.9 or so - hard to say for sure, since it took a while to track down the exact cause. Before that, my system had more than its share of reboots....
    Reply to this comment