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 490252 - crash in System Monitor: I clicked on the system ...
crash in System Monitor: I clicked on the system ...
Status: RESOLVED DUPLICATE of bug 505567
Product: system-monitor
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-25 19:04 UTC by armando
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description armando 2007-10-25 19:04:47 UTC 
Version: 2.20.1

What were you doing when the application crashed?
I clicked on the system monitor applet (cpu graph), and the system monitor program had just loaded, one second passed, and then it crashed.

As an aside, I've been watching system monitor, since system monitor itself seems to be causing periodic spikes that last for about 10 seconds.  This may or may not be related.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.20.1 2007-10-25 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.1-tuxonice-3.0-rc1 #7 SMP PREEMPT Wed Oct 24 15:53:40 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 33280000 vsize: 33280000 resident: 18534400 share: 9445376 rss: 18534400 rss_rlim: 4294967295
CPU usage: start_time: 1193338922 rtime: 8 utime: 3 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1238624528 (LWP 21878)]
0xb7fc0410 in __kernel_vsyscall ()

+ Trace 172846

Thread 1 (Thread -1238624528 (LWP 21878))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 __kernel_vsyscall
  • #10 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #11 *__GI_abort
    at abort.c line 88
  • #12 IA__g_logv
    at gmessages.c line 497
  • #13 IA__g_log
    at gmessages.c line 517
  • #14 main
    at procman.cpp line 689
  • #15 __libc_start_main
    at libc-start.c line 229
  • #16 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (41 sec old) ---------------------
Find Items 0
bbdb: Buddy list has changed since last sync.
bbdb: Buddy list has changed since last sync.
bbdb: Synchronizing buddy list to contacts...
bbdb: Done syncing buddy list to contacts.
bbdb: Synchronizing buddy list to contacts...
bbdb: Done syncing buddy list to contacts.
<EDITTED THIS OUT; related to email addresses>
--------------------------------------------------
Comment 1 Benoît Dejean 2008-01-11 11:11:06 UTC 

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