Comment 6 for bug 1195595

Revision history for this message
Lars Karlitski (larsu) wrote :

Found it. The service leaks DBusmenuItems (user_menuitem_new) like crazy. Each of those connects to the 'notify' signal of a dbus proxy. GLib then uses 100% CPU to dispatch a notify event to all these listeners.

Haw, thanks for your backtrace. It's the same issue.

Killing the service (`killall indicator-session-service`) will make your system usable again without having to logout. However, it will come back to using 100% CPU quite fast.

A hack way to work around this until we have a fix is to rename /usr/lib/indicator-session/indicator-session-service (and kill the running process). NOTE: this will make your session menu unusable.