Package:  panel
Severity: grave
Version:  1.2.4
Synopsis: Panel core dumped during normal operation while system busy
Class:    sw-bug

Distribution: Red Hat Linux release 7.0 (Guinness)
System: Linux 2.2.17-14 i586 unknown
C library: glibc-2.2-12
C compiler: 2.96
glib: 1.2.8
GTK+: 1.2.8
ORBit: ORBit 0.5.6
gnome-libs: gnome-libs 1.2.8
libxml: 1.8.10
gnome-print: gnome-print-0.25-8_helix_1
gnome-core: gnome-core 1.2.4


Description:
The panel core dumped during normal operation while the
system was busy and Netscape was attempting to redraw
a page.

Immediately prior to the core dump, the tasklist applet core
dumped and i got then got two boxes which said, roughly,
"Start gnome panel?  There is already a panel running."

The display is on an ethernet connected NCD X terminal.  It
has 16 Mbyte of ram and is currently very low on space for
display of additional windows.  For example, trying to start
xpdf on a large file receives:

X Error of failed request:  BadAlloc (insufficient resources for
operation)

The computer is a 120 MHz Pentium with 32 Mbyte of ram that
is currently busily paging.  Despite these memory limitations the
system is typically quite reliable.

This problem has occurred to before, and seems to be related to
heavy system paging activity, rather the creation of windows.

Currently, with the panel "crashed", the panel is sort of blinking
in and out of existance.  There is a grey bar where it belongs,
and every 20 sec or arrows appear on each end of it, and then
promptly disappear.


Debugging information:
(no debugging symbols found)...(no debugging symbols found)...
0x405fd869 in __wait4 () from /lib/libc.so.6

+ Trace 8306

------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-08-10 12:52 -------

The original reporter (charmer@punchdown.org) 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, panel-maint@bugzilla.gnome.org.