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.
-- polkitd Memory leak / cpu leak https://bugs.launchpad.net/bugs/662853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
