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


Click here to return to the 'Handle growing SystemUIServer memory usage' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Handle growing SystemUIServer memory usage
Authored by: sfgecko on Sep 20, '10 09:55:13AM

are you sure it's not another menubar app (e.g. google notifier) that is causing your systemuiserver process to leak memory?

i use istat menus 3.05 and my mac has been up for nearly 3 weeks (never sleeps) and systemuiserver is only 150MB. i have 6 other apps that run in the menubar as well, so 150MB doesn't seem unreasonable. it's second only to kernel_task in terms of real memory usage by the system.



[ Reply to This | # ]
Handle growing SystemUIServer memory usage
Authored by: dilvish1984 on Sep 20, '10 11:09:22AM

I'm also not seeing this memory leak with iStat v3.05 -- I'm wondering if the original poster actually submitted this as a bug report to them? They have a nice web form for contacting them at:

http://bjango.com/contact/

I mentioned this thread to them using that web form so maybe someone from Bjango will show up here to comment...

Edited on Sep 20, '10 11:10:37AM by dilvish1984



[ Reply to This | # ]
Handle growing SystemUIServer memory usage
Authored by: ctwise on Sep 20, '10 12:10:11PM

I'm seeing the same behavior. My SystemUIServer was at 1.5 GB (that's not a typo, GB) this morning. It probably depends on which menubar widgets you're using. I have network, CPU, date, disk and battery running. I haven't tried mix and matching to see which might be causing the problem.



[ Reply to This | # ]
Handle growing SystemUIServer memory usage
Authored by: PhotonPanda on Sep 20, '10 10:23:41PM

I have seen this memory leak when I was using 2.x. I fiddled around with the various monitors to try and figure things out. It's not enough to just use or not use some of the monitors. For example, the rate of leak (if it happens for a particular monitor) can be different depending on the display style you choose for that particular monitor. i.e. Using a percentage display for CPU vs using the history histogram.

Since going to 3.x I have not seen the leak no matter which style or monitors I use. The computers used for observation are on for as long as possible - years if possible, but with some scheduled down time.



[ Reply to This | # ]