System monitor freezes up when switching to Processes tab

Bug #881955 reported by Holger Knust
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Gnome-system-monitor 3.20 becomes unresponsive when I switch to the Processes tab. Any other tab works. This is reproducible as it happens every time. The app does not crash but seems to hang in a loop. I am running Oneiric x64

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-system-monitor 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Wed Oct 26 07:03:31 2011
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110804)
SourcePackage: gnome-system-monitor
UpgradeStatus: Upgraded to oneiric on 2011-09-11 (44 days ago)

Revision history for this message
Holger Knust (hknust) wrote :
Revision history for this message
trent-- (sylvainfaivre) wrote :

I am having the same problem with gnome-system-monitor 3.2.1-0ubuntu1 on Oneiric with a 3.0.0-12-generic kernel.
Here is a trace file.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-system-monitor (Ubuntu):
status: New → Confirmed
Revision history for this message
Petar Velkovski (pvelkovski) wrote :
Download full text (6.6 KiB)

After doing some testing on my system, I realized that this problem occurs if you have xorg-edgers PPA activated. Purging the PPA solves the problem. This is the list of packages that the xorg-edgers PPA upgrades:

intel-gpu-tools (1.0.2+git20100324-0ubuntu1) to 1.0.2+git20110729+3b10b7b-0ubuntu1~edgers
libcairo-gobject2 (1.10.2-6ubuntu3) to 1.11.3+git20111109.90b2fd34-0ubuntu0ricotz~oneiric0
libcairo-script-interpreter2 (1.10.2-6ubuntu3) to 1.11.3+git20111109.90b2fd34-0ubuntu0ricotz~oneiric0
libcairo2 (1.10.2-6ubuntu3) to 1.11.3+git20111109.90b2fd34-0ubuntu0ricotz~oneiric0
libcairo2-dev (1.10.2-6ubuntu3) to 1.11.3+git20111109.90b2fd34-0ubuntu0ricotz~oneiric0
libdrm-dev (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libdrm-intel1 (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libdrm-nouveau1a (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libdrm-radeon1 (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libdrm2 (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libegl1-mesa (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libegl1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libegl1-mesa-drivers (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libffi6 (3.0.11~rc1-2) to 3.0.11~rc1-5~oneiric1
libgbm1 (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libgl1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libgl1-mesa-dri (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libgl1-mesa-glx (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libglapi-mesa (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libglu1-mesa (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libglu1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libkms1 (2.4.26-1ubuntu1) to 2.4.27+git20111104.961bf9b5-0ubuntu0sarvatt~oneiric
libopenvg1-mesa (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
libpciaccess0 (0.12.1-2) to 0.12.902-0ubuntu0ricotz~oneiric0
libpixman-1-0 (0.22.2-1) to 0.24.0-1~oneiric1
libpixman-1-dev (0.22.2-1) to 0.24.0-1~oneiric1
libwayland0 (0.1.0~0.2-0ubuntu3) to 0.1.0~git20111027.7e57dc14-0ubuntu0ricotz~oneiric
linux-libc-dev (3.0.0-13.22) to 3.1.0-2.2
linux-tools-common (3.0.0-13.22) to 3.1.0-2.2
mesa-common-dev (7.11-0ubuntu3) to 7.12.0~git20111109.1d1c0fa2-0ubuntu0sarvatt~oneiric
nvidia-current (285.05.09-0ubuntu1~oneiric~xup1) to 290.06-0ubuntu1~xedgers~oneiric1
nvidia-settings (285.05.09-0ubuntu1~oneiric~xup1) to 290.06-0ubuntu1~xedgers~oneiric1
x11-common (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2
xorg (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2
xserver-common (2:1.10.4-1ubuntu4.2) to 2:1.11.2+git20111109+server-1.11-branch.34bb83b9-0ubuntu0ricotz~oneiric
xserver-xorg (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2
xserver-xorg-core (2:1.10.4-1ubuntu4.2) to 2:1.11.2+git20111109+server-1.11-branch.34bb83b9-0ubuntu0ricotz~oneiric
xserver-xorg-input-all (1:7.6+7ubuntu7) to 1:7.6+7ubuntu...

Read more...

Revision history for this message
markb (mark-blakeney) wrote :

I am running Oneiric x32 with nvidia driver and also get this problem when I enable xorg-edgers ppa. Purging that ppa removes the problem. Does not happen on my intel video laptop with same ppa enabled so seems xorg-edgers + nvidia (290.06) related?

System monitor lock up is repeatable but other GTK apps lock up also, e.g. transmission. When it locks up in transmission sometimes my entire gnome-shell session locks up and I must kill it from a console.

Revision history for this message
markb (mark-blakeney) wrote :

Not sure if helpful but further to my above comment I find that gnome-system-monitor locks up in a futex() call:

stat64("/proc/2426", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
stat64("/proc/2427", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
stat64("/proc/2500", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
stat64("/proc/2501", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
stat64("/proc/2506", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
getdents(14, /* 0 entries */, 32768) = 0
close(14) = 0
open("/proc/stat", O_RDONLY) = 14
read(14, "cpu 7326 189 2427 91947 15582 0"..., 8191) = 1787
read(14, "", 6404) = 0
close(14) = 0
stat64("/proc/1707", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
open("/proc/1707/stat", O_RDONLY) = 14
read(14, "1707 (gnome-session) S 1157 1707"..., 8191) = 224
read(14, "", 7967) = 0
close(14) = 0
open("/proc/1707/stat", O_RDONLY) = 14
read(14, "1707 (gnome-session) S 1157 1707"..., 8191) = 224
read(14, "", 7967) = 0
close(14) = 0
open("/proc/1707/cpu", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/proc/1707/cmdline", O_RDONLY|O_LARGEFILE) = 14
fstat64(14, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl64(14, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat64(14, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb3feb000
_llseek(14, 0, [0], SEEK_CUR) = 0
read(14, "/usr/bin/gnome-session\0--session"..., 4096) = 39
read(14, "", 3072) = 0
close(14) = 0
munmap(0xb3feb000, 4096) = 0
open("/proc/1707/attr/current", O_RDONLY|O_LARGEFILE) = 14
read(14, "unconfined\n", 4095) = 11
close(14) = 0
futex(0xb62c8b64, FUTEX_WAKE_PRIVATE, 2147483647) = 0

Sits on last line above at 100% cpu.

If I run transmission-gtk under strace then it won't fail but if I run it normally and then attach strace after it locks up, then it is also sitting on a futex() call at 100% cpu (although in this case it also hangs my gnome-shell session).

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

Packages from the xorg-edgers PPA also made Gnome Shell crash on my computer when switching from Windows to Applications "tab".
I also noticed increased memory usage on my computer. In normal circumstances 31% of my system memory (out of 2GB) would be used after an X server reset (CTRL+ALT+BACKSPACE) and logging into Gnome Shell, but with the PPA enabled the memory usage refused to go under 51% after a reset (I tried it multiple times), and this happened after using the computer for a few hours. But I couldn't see what was using the memory because you know ..... Gnome system monitor isn't working :).

Revision history for this message
Holger Knust (hknust) wrote :

Nice find!

Xorg-edgers ppa is installed on my latpop. Mark Blakeney reported that it affects his Nvidia system but not Intel. My laptop uses the Optimus technology where the Intel HD 3000 chip is the main display hardware and the Nvidia chip is dormant for the most part unless you use bumblebee. Yet, the problem occurs.

Revision history for this message
trent-- (sylvainfaivre) wrote :

I had nvidia and xorg related packages from the xorg-edgers ppa too. Purging the ppa resolved this bug for me too.
Thanks for the heads up.

Revision history for this message
Robert Roth (evfool) wrote :

Based on the discussion from the comments, seems that the issue is related to xorg-edgers ppa packages, so this is not System Monitor related, thus I am closing this bug as Invalid.

Changed in gnome-system-monitor (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.