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 100257 - After running for days, system came down to grinding hault, Every time I start gtop, it crashes right after
After running for days, system came down to grinding hault, Every time I star...
Status: RESOLVED DUPLICATE of bug 65455
Product: gtop
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Martin Baulig
Martin Baulig
Depends on:
Blocks:
 
 
Reported: 2002-12-03 18:46 UTC by Yanglong Zhu
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yanglong Zhu 2002-12-03 18:44:24 UTC 
Package: gtop [gnome-system-monitor]
Severity: normal
Version: 1.0.13
Synopsis: After running for days, system came down to grinding hault, Every time I start gtop, it crashes right after
Bugzilla-Product: gtop [gnome-system-monitor]
Bugzilla-Component: general

Description:
After running for days, the system rh7.3 came down to grinding hault, Every time I start gtop, it crashes right after. Top still works, but I couldn't find any time consuming processes running there. System monitor shows the CPU is not busy at all. But the harddrive indicator (light) is on all the time and it is busy.

One thing may of importance: I opened a piece of huggggge email from myself, which contains a dozen digital pictures (30-40 MB in total). When I notice the system is unhappy with the huge email, I deleteed it immediately. And the system seemed to recovered pretty soon.

That's when I left for the day (night). When I come back 8 hours later, I found the grinding haulted system.


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x420b48b9 in wait4 () from /lib/i686/libc.so.6

+ Trace 31247

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gtk_label_finalize_lines
    from /usr/lib/libgtk-1.2.so.0
  • #5 gtk_label_size_request
    from /usr/lib/libgtk-1.2.so.0
  • #6 gtk_marshal_NONE__POINTER
    from /usr/lib/libgtk-1.2.so.0
  • #7 gtk_signal_real_emit
    from /usr/lib/libgtk-1.2.so.0
  • #8 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #9 gtk_widget_size_request
    from /usr/lib/libgtk-1.2.so.0
  • #10 gtk_widget_set_style_internal
    from /usr/lib/libgtk-1.2.so.0
  • #11 gtk_widget_set_style
    from /usr/lib/libgtk-1.2.so.0
  • #12 procview_type_set
  • #13 procview_new
  • #14 gtop_procview_new
  • #15 gtop_page_get_type
  • #16 gnome_mdi_child_create_view
    from /usr/lib/libgnomeui.so.32
  • #17 gnome_mdi_child_add_view
    from /usr/lib/libgnomeui.so.32
  • #18 gnome_mdi_add_view
    from /usr/lib/libgnomeui.so.32
  • #19 gtop_mdi_start
  • #20 main
  • #21 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gtk_label_finalize_lines
    from /usr/lib/libgtk-1.2.so.0
  • #5 gtk_label_size_request
    from /usr/lib/libgtk-1.2.so.0
  • #6 gtk_marshal_NONE__POINTER
    from /usr/lib/libgtk-1.2.so.0
  • #7 gtk_signal_real_emit
    from /usr/lib/libgtk-1.2.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-03 13:44 -------

Unknown version 1.0.x in product gtop [gnome-system-monitor]. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, martin@gnome.org.
Comment 1 Elijah Newren 2002-12-03 19:38:24 UTC 

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