gnome-system-monitor "Memory Maps"-window blocking interdependent from the showing process

Bug #338564 reported by Lödur
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-monitor

The blocking case:
1. In the GNOME Panel click on "System", choose "Administration >" and click on "System Monitor"
2. Click on the tab _/Processes\_
3. Right-click on the process "gnome-system-monitor" and click on "Memory Maps"
4. In "Memory-Maps"-window scroll down to the end of the spreadsheet

-> Now "Memory-Maps"-window is blocking and not respond
/!\ I can just use "Forced Quit" to close

The running case:
1. In the GNOME Panel click on "System", choose "Administration >" and click on "System Monitor"
2. Click on the tab _/Processes\_
3. Right-click on the process "dbus-launch" and click on "Memory Maps"
4. In "Memory-Maps"-window scroll down to the end of the spreadsheet

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-system-monitor
Package: gnome-system-monitor 2.26.0-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
Uname: Linux 2.6.28-8-generic i686

Revision history for this message
Lödur (loedur) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, I'm not confirming the issue on jaunty though, do you have any error on the command line if you run gnome-system-monitor there?

Changed in gnome-system-monitor:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Lödur (loedur) wrote :

Hallo,

I have the same issue if I run gnome-system-monitor on the command line.

Following displayed on terminal:
** (gnome-system-monitor:5717): WARNING **: SELinux was found but is not enabled.

Revision history for this message
Lödur (loedur) wrote :

Hallo,

the error no longer occurs.

o Ubuntu 9.04
o Linux 2.6.28-15-generic
o System Monitor 2.26.0.1

Changed in gnome-system-monitor (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I'm seeing this in Karmic, Version: 2.28.0-0ubuntu1
(64bit) - since you marked as fixed release just because it seemed to go for you, I'm moving this to confirmed.

backtrace:

#0 0x00007f853d0b7338 in *__GI___poll (fds=0x10da840, nfds=6,
    timeout=<value optimised out>) at ../sysdeps/unix/sysv/linux/poll.c:83
#1 0x00007f853db3d36c in ?? () from /lib/libglib-2.0.so.0
#2 0x00007f853db3d6b0 in g_main_context_iteration ()
   from /lib/libglib-2.0.so.0
#3 0x00007f853cda1ca4 in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#4 0x00007f853cda67c5 in ORBit_small_invoke_stub ()
   from /usr/lib/libORBit-2.so.0
#5 0x00007f853419b02c in Accessibility_EventListener_notifyEvent ()
   from /usr/lib/libspi.so.0
#6 0x00007f85343d803a in ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#7 0x00007f85343d8893 in ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#8 0x00007f853dde7421 in ?? () from /usr/lib/libgobject-2.0.so.0
#9 0x00007f853dde8d39 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#10 0x00007f853dde90a4 in g_signal_emit_by_name ()
   from /usr/lib/libgobject-2.0.so.0
#11 0x00007f8534817f1d in model_row_deleted (tree_model=0x13aff40,
    path=<value optimised out>, user_data=<value optimised out>)
    at /build/buildd/gtk+2.0-2.18.3/modules/other/gail/gailtreeview.c:2974
#12 0x00007f853ddd25ae in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#13 0x00007f853dde7f70 in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0x00007f853dde8d39 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#15 0x00007f853dde9283 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#16 0x00007f853fbbbb5e in IA__gtk_list_store_remove (list_store=0x13aff40,
    iter=0x7fff5e812570) at /build/buildd/gtk+2.0-2.18.3/gtk/gtkliststore.c:974
#17 0x0000000000423970 in ?? ()
#18 0x000000000042427a in ?? ()
#19 0x00007f853db3a2cb in ?? () from /lib/libglib-2.0.so.0
#20 0x00007f853db39bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x00007f853db3d588 in ?? () from /lib/libglib-2.0.so.0
#22 0x00007f853db3d9e5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#23 0x00007f853fbbf177 in IA__gtk_main ()
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c:1218
#24 0x00000000004124a0 in ?? ()
#25 0x00007f853d002abd in __libc_start_main (main=<value optimised out>,
    argc=<value optimised out>, ubp_av=<value optimised out>,
    init=<value optimised out>, fini=<value optimised out>,
    rtld_fini=<value optimised out>, stack_end=0x7fff5e812aa8)
    at libc-start.c:220
#26 0x00000000004109a9 in ?? ()
#27 0x00007fff5e812aa8 in ?? ()
#28 0x000000000000001c in ?? ()
#29 0x0000000000000001 in ?? ()
#30 0x00007fff5e813b8a in ?? ()
#31 0x0000000000000000 in ?? ()

for reference the process was exaile which is using vast amounts of ram, but doesn't have that many maps in /proc/pid/maps

Dave

Changed in gnome-system-monitor (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

This seems to be OK for me now on Oneiric - everyone else happy?

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

It doesn't happen to Precise neither, started Exaile and opened memory maps, scrolled down to the end, but the app didn't crash, so I'd say it's fixed, marking it as such. Please reopen if this still happens for you.

Changed in gnome-system-monitor (Ubuntu):
status: Confirmed → Fix Released
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.