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 81648 - System Monitor Hangs
System Monitor Hangs
Status: RESOLVED DUPLICATE of bug 71374
Product: system-monitor
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-13 15:46 UTC by Duncan Innes
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Duncan Innes 2002-05-13 14:46:10 UTC
Package: system-monitor [was: procman]
Severity: normal
Version: 1.1.6
Synopsis: System Monitor Hangs
Bugzilla-Product: system-monitor [was: procman]
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (1.116.1)

Description:
Description of Problem: System monitor hung when scrolling upwards on
the list of all processes


Steps to reproduce the problem:
1. Notice that the CPU load in the System Monitor toolbar graph is
showing 50% user and 50% system
2. Right click on the graph to bring up the detailed system monitor
3. Fart around trying to find rogue process - then notice that you're
only looking at your own processes
4. Select the "View All Processes" option from the combo box
5. try to scroll up the screen as the browse widget now is positioned in
the middle of the list
6. System Monitor hangs and puts up Bug Buddy

Actual Results:


Expected Results:


How often does this happen? Just the once when I noticed that the CPU
load applet was showing roughly 50% user and 50% system time
consistently for 10 mins.  I went to the detailed system monitor to find
out what was going on and when I clicked on "Show All Processes" and
then tried to scroll upwards, the process hung and came up with the
bug-buddy screen.


Additional Information: I don't think this is a serious bug - more of a
process hanging and taking the system monitor with it.  I only report it
in case there is an underlying problem with some GNOME 2 code.  I had
only recently swithced the PC on, and had done no more than check my
e-mails with Evolution and run Red Carpet to find any new updates - so
there should not have been any rogue processes.




Debugging Information:

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

[New Thread 1024 (LWP 4085)]
0x407fe319 in __wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 4085))

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/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-13 10:46 -------

The original reporter (duncan@innes.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, kfv101@psu.edu.

Comment 1 Luis Villa 2002-05-13 17:45:02 UTC
Kevin: BTW, is this yet another variant of 71374?
Comment 2 Kevin Vandersloot 2002-05-15 23:09:01 UTC

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