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 421636 - crash in System Monitor: I was reading an article...
crash in System Monitor: I was reading an article...
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: 2007-03-22 20:41 UTC by sigmadraconis
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sigmadraconis 2007-03-22 20:41:34 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I was reading an article at rahoi.com in Firefox, while a Flash presentation was loading. After several sec I knew something was wrong b/c the "system busy" cursor kept spinning, I couldn't stop the process or quit Firefox, and finally did a CTL-ALT-BACKSPACE to reset. Afterwards, the system said FF was still running, but I didn't see it in the tray or in System Monitor  -- then Sys Monitor itself hung and I had to Force Quit. 

Not sure what is going on here, if it is software related or if I have a hardware issue... Thanks for checking into it. 



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

Memory status: size: 54534144 vsize: 0 resident: 54534144 share: 0 rss: 15544320 rss_rlim: 0
CPU usage: start_time: 1174595075 rtime: 0 utime: 514 stime: 0 cutime:442 cstime: 0 timeout: 72 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 -1225222480 (LWP 6010)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 121258

Thread 1 (Thread -1225222480 (LWP 6010))

  • #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


Susana





          2007-03-22 23:02:41 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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