Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Thanks! | 18 comments | Create New Account
Click here to return to the 'Thanks!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Authored by: CarlRJ on Sep 20, '10 10:22:11AM

I haven't tested the LaunchDaemon, but I have little doubt it would work -- I found this page googling about SystemUIServer and memory usage, and can happily report that "killall SystemUIServer" does indeed (temporarily at least) solve my problem.

I had been a little suspicious of iStat Menus (which I'd rather not forgo -- too useful), as it was the only non-Apple thing I saw referenced in SystemUIServer's open files list in Activity Monitor.

Thanks, name99, very much, for doing/presenting the research that SystemUIServer can safely be killed (and will auto-restart), as I was not looking forward to having to restart my MBP occasionally just to get SystemUIServer to release its excess memory.

And I was a little astonished to find precisely the answer I needed, written up on the very morning I went looking for it. BTW, I also came across Tuning Mac OS X Performance, which suggests that 3rd-party menu extras are top suspects in excess CPU usage by SystemUIServer as well:

Third-party menu extras that use an active Internet connection can result in very high CPU usage if the network connection becomes busy or blocked. The chances of this increase if you are simultaneously using streaming media and a menu extra that requires an Internet connection.

[ Reply to This | # ]