tombrus
October 31st, 2009, 09:09 PM
After upgrading to Karmic I noticed my CPU to be busy all the time.
After some investigation I noticed that at-spi-registryd and dbus-daemon are both nibbling away around 20%-30% of my CPU power.
Furthermore I noticed that indicator-messages and at-spi-registryd are using serious amounts of memory and are continuously asking for more. I would say they are leaking memory.
Here are two top snippets a few minutes appart:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2390 tom 20 0 947m 816m 4644 R 27 20.6 180:22.92 at-spi-registry
1870 tom 20 0 66856 40m 640 R 22 1.0 334:54.50 dbus-daemon
2806 tom 20 0 541m 481m 2756 S 5 12.2 78:26.65 indicator-messa
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2390 tom 20 0 963m 832m 4640 S 28 21.0 185:30.41 at-spi-registry
1870 tom 20 0 66856 40m 640 S 25 1.0 339:10.95 dbus-daemon
2806 tom 20 0 545m 486m 2756 S 6 12.3 79:21.98 indicator-messa
Is this the general experience?
Is there a bug for this already?
Does anybody know a workaround?
I can work with my machine alright, but if I leave it running for too long (and I tend to leave it running indefinitely) it will probably eat itself through all the available memory :(. So I am forced to restart every so many days (like you have (had?) to do with windose ;))
-Tom
After some investigation I noticed that at-spi-registryd and dbus-daemon are both nibbling away around 20%-30% of my CPU power.
Furthermore I noticed that indicator-messages and at-spi-registryd are using serious amounts of memory and are continuously asking for more. I would say they are leaking memory.
Here are two top snippets a few minutes appart:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2390 tom 20 0 947m 816m 4644 R 27 20.6 180:22.92 at-spi-registry
1870 tom 20 0 66856 40m 640 R 22 1.0 334:54.50 dbus-daemon
2806 tom 20 0 541m 481m 2756 S 5 12.2 78:26.65 indicator-messa
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2390 tom 20 0 963m 832m 4640 S 28 21.0 185:30.41 at-spi-registry
1870 tom 20 0 66856 40m 640 S 25 1.0 339:10.95 dbus-daemon
2806 tom 20 0 545m 486m 2756 S 6 12.3 79:21.98 indicator-messa
Is this the general experience?
Is there a bug for this already?
Does anybody know a workaround?
I can work with my machine alright, but if I leave it running for too long (and I tend to leave it running indefinitely) it will probably eat itself through all the available memory :(. So I am forced to restart every so many days (like you have (had?) to do with windose ;))
-Tom