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 81572 - spontaneous crash
spontaneous crash
Status: RESOLVED DUPLICATE of bug 71374
Product: system-monitor
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-12 19:18 UTC by Ben Liblit
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ben Liblit 2002-05-12 19:18:21 UTC 
Package: system-monitor [was: procman]
Severity: normal
Version: 1.1.6.0.200205071406-0.snap.ximian.1
Synopsis: spontaneous crash
Bugzilla-Product: system-monitor [was: procman]
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (1.116.1)

Description:
Description of Problem:

The system monitor had been running for a few seconds, showing me a list
of active processes sorted by CPU utilization.  Boom, crash.  No user
input; it died on its own.

How often does this happen?

Just once, so far....



Debugging Information:

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

[New Thread 1024 (LWP 8125)]
0x408031d9 in __wait4 () from /lib/i686/libc.so.6

+ Trace 22059

Thread 1 (Thread 1024 (LWP 8125))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 593
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-12 15:18 -------

Reassigning to the default owner of the component, kfv101@psu.edu.
Comment 1 Luis Villa 2002-05-12 22:47:23 UTC 

*** This bug has been marked as a duplicate of 71374 ***
Comment 2 Ben Liblit 2004-11-18 08:37:51 UTC 
Why has the component for this bug been changed to "docs"?  This is not a
documentation problem.  The application crashed outright.  Documentation has
nothing to do with it.