Bug 393322 – crash in System Monitor:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 393322 - crash in System Monitor:


Summary:	crash in System Monitor:


Status:	RESOLVED DUPLICATE of bug 364839

Product:	system-monitor
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-05 23:40 UTC by aoki
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description aoki 2007-01-05 23:40:29 UTC

Version: 2.17.4.2

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2904.fc7 #0 SMP Fri Jan 5 19:04:51 JST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 346079232 vsize: 346079232 resident: 31891456 share: 15638528 rss: 31891456 rss_rlim: -1
CPU usage: start_time: 1168039986 rtime: 1025 utime: 893 stime: 132 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-monitor'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912513152448 (LWP 3470)]
(no debugging symbols found)
0x0000003c8c80d7c5 in waitpid () from /lib64/libpthread.so.0

+ Trace 99725

Thread 1 (Thread 46912513152448 (LWP 3470))

#0 waitpid
from /lib64/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strlen
from /lib64/libc.so.6
#4 giop_send_buffer_append_string
from /usr/lib64/libORBit-2.so.0
#5 ORBit_marshal_value
from /usr/lib64/libORBit-2.so.0
#6 ORBit_marshal_value
from /usr/lib64/libORBit-2.so.0
#7 ORBit_marshal_any
from /usr/lib64/libORBit-2.so.0
#8 ORBit_marshal_value
from /usr/lib64/libORBit-2.so.0
#9 ORBit_marshal_value
from /usr/lib64/libORBit-2.so.0
#10 ORBit_small_allocbuf
from /usr/lib64/libORBit-2.so.0
#11 ORBit_small_invoke_stub
from /usr/lib64/libORBit-2.so.0
#12 Accessibility_EventListener_notifyEvent
from /usr/lib64/libspi.so.0
#13 __cxa_pure_virtual
from /usr/lib64/gtk-2.0/modules/libatk-bridge.so
#14 __cxa_pure_virtual
from /usr/lib64/gtk-2.0/modules/libatk-bridge.so
#15 exit
from /lib64/libc.so.6
#16 __libc_start_main
from /lib64/libc.so.6
#17 __cxa_pure_virtual
#18 ??
#19 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Christian Kirbach 2007-01-05 23:55:48 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 364839 ***