Comment 5 for bug 662853
Revision history for this message
| Brandon Williams (opensource-subakutty) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
In my case, high memory/CPU utilization in polkitd and CPU utilization in dbus was the result of repeated calls to nm-tool that I was making in conky to determine my wireless essid. In previous versions, this was not a problem, and there is clearly a memory leak in polkitd associated with this. However, I can work around the problem by dropping the calls to nm-tool from my conky config.