Program backend consumes more than 90% CPU after System Testing

[Roman Khatko]

Binary package hint: checkbox

Ubuntu 10.04 (06.04.2010 image from iso.qa.ubuntu.com)

Program backend consumes more than 90% CPU.

Steps to reproduce:
Open: System - System Testing
click Next, wait and Close (first time I run all tests - same result).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: checkbox 0.9.1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CheckboxSubmission: 2ff96c0dba09db72890a904020d1525b
CheckboxSystem: b62ae224500b03a9fc2c9b6caf3feb14
Date: Tue Apr 6 16:00:13 2010
ExecutablePath: /usr/share/checkbox/backend
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406)
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SourcePackage: checkbox

[Stephan Peijnik (speijnik)]

I can confirm this issue. After closing checkbox its backend continues running and gives the CPU quite a lot work.

[Roman Friesen (krokosjablik)]

I can confirm this issue too, CPU usage 100%.
After one hour after the checkbox tests the problem with 100% CPU usage is still there (here there are two CPU's, therefore 103%):

ubuntu@ubuntu:~$ top
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 4834 root 20 0 8180 4444 2080 R 103 0.2 13:49.49 backend

ubuntu@ubuntu:~$ ps -ef | grep backend
root 4834 1 60 11:29 ? 00:23:36 /usr/bin/python /usr/share/checkbox/backend /tmp/checkboxXsBELT/input /tmp/checkboxXsBELT/output

[Roman Friesen (krokosjablik)]

ah, I have tested the live system lucid beta 2.

[traeumer (pirat) (spamundso)]

Ubuntu 10.04 (final + installed all available updates)
Same here.
After starting and closing "system testing" applicating, top tells me this:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1949 root 20 0 8056 4340 2048 R 99 0.4 0:47.79 backend

[Pera Zdera (simplify)]

Confirming problem.
 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2056 root 20 0 26948 6060 2364 R 100 0.1 29469:31 backend
22705 root 20 0 26948 6128 2464 R 100 0.1 1:05.64 backend

I have "backend" process running for a while. I started the System->Administration->System Testing. Deselected all tests and moved to finish. Aplication closed and left another "backend" process behaind

uname -a:
Linux <HOSTNAME< 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

lscpu:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU(s): 4
Thread(s) per core: 2
Core(s) per socket: 2
CPU socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 37
Stepping: 2
CPU MHz: 3201.000
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 4096K

Peace

[Aris Manginas (babis-sealabs)]

Same here... Never had an issue in previous releases, it stared as soon as i upgraded to 10.04

$ ps -eo pcpu,args|sort -rn|head
81.2 /usr/bin/python /usr/share/checkbox/backend /tmp/checkboxcHjiFY/input /tmp/checkboxcHjiFY/output
10.0 /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-EdfrCB/database -nolisten tcp vt7
 9.0 /usr/lib/libgconf2-4/gconfd-2
 4.8 /bin/dbus-daemon --fork --print-pid 5 --print-address 9 --session
 3.7 /opt/google/chrome/chrome --type=renderer --lang=el --force-fieldtest=CacheSize/CacheSizeGroup_3/DnsImpact/_max_2 concurrent_prefetch/GlobalSdch/_global_enable_sdch/ --channel=5101.0x481aa40.291792407
 2.6 gnome-session
 2.0 evolution
 2.0 compiz --replace
 1.6 gnome-panel
 1.5 python /usr/share/system-config-printer/applet.py

$uname -a
Linux ubuntu 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

$lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU(s): 2
Thread(s) per core: 1
Core(s) per socket: 2
CPU socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Stepping: 11
CPU MHz: 2666.902
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K

[Nixloz (nixloz)]

I only launched the system testing app, but never really started it.
the backend continued after closing the app though causing one of the 2 cores to be at 100% all of the time (occasionally switching core).

[Ole Jon Bjørkum (olejonbj)]

Same here.

[rMatey (anonamouse)]

  Damnit! I got the same problem after System Testing. Using two cores of my Athlon II X3 445 Rana 3.1GH

[Vincenzo Mazzotta (vincenzo-mazzotta-it)]

I have same problem with a X9000 processor
One core 100% second core 28%

This is a bug of programming.

[Vincenzo Mazzotta (vincenzo-mazzotta-it)]

To kil the process and go down frequency cpu:

sudo top
insert administrator password
press k key to kill process and write pid of backend process
insert 9 of type of kill

Ended backend process

[Todor Velichkov (tosho)]

Same Here
$ps -eo pcpu,args|sort -rn|head
97.9 /usr/bin/python /usr/share/checkbox/backend /tmp/checkboxGPLFkK/input /tmp/checkboxGPLFkK/output
10.0 python /usr/share/checkbox/run /usr/share/checkbox/configs/checkbox-gtk.ini
 9.2 /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-nBM0Ac/database -nolisten tcp vt7
 8.5 bash
 3.7 /usr/lib/firefox-3.6.16/firefox-bin
 2.6 gnome-control-center
 2.2 ktorrent --icon ktorrent -caption KTorrent file:///tmp/Unigine_Tropics-1.3.run.torrent
 1.0 gksu -k -- PATH=/usr/share/checkbox/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games /usr/share/checkbox/backend /tmp/checkboxwSI1xv/input /tmp/checkboxwSI1xv/output
 0.9 mono --debug /usr/lib/docky/Docky.exe --debug
 0.4 /usr/bin/pulseaudio --start --log-target=syslog

$top

 9062 root 20 0 26964 6120 2452 R 100 0.2 95:55.82 backend
   992 root 20 0 379m 147m 95m S 4 3.7 17:48.81 Xorg

$uname -a
2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 x86_64 GNU/Linux

$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU(s): 2
Thread(s) per core: 1
Core(s) per socket: 2
CPU socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 10
CPU MHz: 2100.000
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K

[Osmin Abarca (osmin-abarca)]

In terminal use 'top', looks PID of 'backend' (ctrl + c, to ends top) and type 'sudo kill -9 (PID of backend)'
In my case, it was 'sudo kill -9 3533'
This problem starts when, for curiously, I run the application 'System Testing'... and close without do anything.