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 438625 - crash in GNOME System Monitor: After more than 8 hours ...
crash in GNOME System Monitor: After more than 8 hours ...
Status: RESOLVED DUPLICATE of bug 352444
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-15 15:19 UTC by javinovich
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description javinovich 2007-05-15 15:19:22 UTC
Version: 2.16.1

What were you doing when the application crashed?
After more than 8 hours System Monitor crashed.

I left my gnome session opened since yesterday. Now that I arrived at office I tried to restore System Monitor from the taskbar and it simply crashed and the Bug reporting tool was opened.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 370491392 vsize: 370491392 resident: 144138240 share: 9347072 rss: 153485312 rss_rlim: 1785364480
CPU usage: start_time: 1179179670 rtime: 517518 utime: 275644 stime: 241874 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/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 47319463640768 (LWP 19102)]
0x00002b096a900c25 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47319463640768 (LWP 19102))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #8 ORBit_RootObject_duplicate_T
    from /opt/gnome/lib64/libORBit-2.so.0
  • #9 CORBA_free
    from /opt/gnome/lib64/libORBit-2.so.0
  • #10 CORBA_free
    from /opt/gnome/lib64/libORBit-2.so.0
  • #11 ORBit_free_T
    from /opt/gnome/lib64/libORBit-2.so.0
  • #12 ORBit_free
    from /opt/gnome/lib64/libORBit-2.so.0
  • #13 gnome_accessibility_module_shutdown
    from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
  • #14 gnome_accessibility_module_shutdown
    from /opt/gnome/lib64/gtk-2.0/modules/libatk-bridge.so
  • #15 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #18 gail_window_new
    from /opt/gnome/lib64/gtk-2.0/modules/libgail.so
  • #19 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #21 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #24 gtk_widget_event_internal
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #25 gtk_main_do_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #26 gdk_event_dispatch
    from /opt/gnome/lib64/libgdk-x11-2.0.so.0
  • #27 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #28 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #30 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #31 g_object_unref
  • #32 __libc_start_main
    from /lib64/libc.so.6
  • #33 g_object_unref
  • #34 ??
  • #35 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Bruno Boaventura 2007-05-15 21:22:43 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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