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 391037 - crash in System Monitor: Was in the process of in...
crash in System Monitor: Was in the process of in...
Status: RESOLVED DUPLICATE of bug 354559
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: 2006-12-30 17:54 UTC by david
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description david 2006-12-30 17:54:08 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Was in the process of installing some apps and had tried starting ktorrent. However It was not showing up in the tray so I went to investigate in the monitor because overall system performance was suffering. It would not allow me to kill any processes and eventually just locked everything up essentially.	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 33783808 vsize: 0 resident: 33783808 share: 0 rss: 811008 rss_rlim: 0
CPU usage: start_time: 1167500537 rtime: 0 utime: 685 stime: 0 cutime:489 cstime: 0 timeout: 196 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225935184 (LWP 9279)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 98065

Thread 1 (Thread -1225935184 (LWP 9279))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 sexy_tree_view_new
    from /usr/lib/libsexy.so.2
  • #7 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 _IO_stdin_used
  • #15 ??
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2006-12-30 17:59:22 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 354559 ***