Gwibber

  1. Bug #306497
  2. Comment #12

Comment 12 for bug 306497

Revision history for this message
Tom Kopacz (tom-kopacz) wrote :

Gwibber uses an enormous amount of RAM when it's checking my Twitter account and maxes out my dual-core CPU as well.

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
19012 tom 20 0 152m 16m 2500 S 17 0.9 0:01.86 gwibber-service
19007 tom 20 0 128m 16m 2572 S 15 0.9 0:02.55 gwibber-service
19003 tom 20 0 104m 16m 2572 S 13 0.9 0:02.74 gwibber-service
18997 tom 20 0 104m 16m 2576 S 12 0.9 0:04.57 gwibber-service
19013 tom 20 0 152m 16m 2612 S 11 0.9 0:01.27 gwibber-service
19002 tom 20 0 104m 17m 2760 S 11 0.9 0:02.05 gwibber-service
19017 tom 20 0 176m 16m 2500 S 11 0.9 0:01.06 gwibber-service
19018 tom 20 0 176m 16m 2484 S 10 0.9 0:01.05 gwibber-service

It takes up so many processor cycles that it pushes the temperature sensors on my AMD Turion64x2 from about its normal operating range of 120° to well over 140°. I've taken Facebook off Gwibber and that helps a little, but not much. Here it is with Facebook added back in.

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
19040 tom 20 0 202m 88m 25m R 64 4.7 0:16.24 gwibber
 2073 tom 20 0 74220 16m 3144 S 47 0.9 23:37.28 beam.smp
19157 tom 20 0 200m 16m 2572 S 17 0.9 0:03.12 gwibber-service
19158 tom 20 0 200m 16m 2612 S 14 0.9 0:02.15 gwibber-service

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2073 tom 20 0 76116 15m 3144 S 49 0.8 23:48.82 beam.smp
19242 tom 20 0 200m 16m 2520 S 27 0.9 0:02.09 gwibber-service
19228 tom 20 0 176m 16m 2520 R 15 0.9 0:02.22 gwibber-service
19219 tom 20 0 152m 16m 2572 R 14 0.9 0:02.88 gwibber-service
19210 tom 20 0 104m 16m 2576 S 13 0.9 0:03.45 gwibber-service
19243 tom 20 0 200m 16m 2520 S 13 0.9 0:01.04 gwibber-service
19215 tom 20 0 128m 16m 2572 R 10 0.9 0:03.15 gwibber-service
19220 tom 20 0 152m 16m 2612 S 9 0.9 0:02.10 gwibber-service
19209 tom 20 0 104m 16m 2612 S 9 0.9 0:02.63 gwibber-service
19229 tom 20 0 176m 16m 2612 R 8 0.9 0:01.69 gwibber-service
19040 tom 20 0 202m 88m 25m R 6 4.7 0:22.51 gwibber
19214 tom 20 0 128m 16m 2612 R 5 0.9 0:02.41 gwibber-service

So I have it as gwibber, gwibber-service and an apparently-related process called "beam.smp" ... which also has a bug report in Launchpad for using lots of processor cycles on CouchDB contacts lookup: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/458453