Version: 2.18.2

What were you doing when the application crashed?
browsing the web :-)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 873603072 vsize: 873603072 resident: 204832768 share: 33959936 rss: 204832768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182266658 rtime: 81786 utime: 78237 stime: 3549 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496349776 (LWP 2976)]
[New Thread 1178638672 (LWP 5958)]
[New Thread 1147169104 (LWP 5952)]
[New Thread 1115699536 (LWP 5951)]
[New Thread 1136679248 (LWP 5950)]
[New Thread 1168148816 (LWP 2996)]
[New Thread 1157658960 (LWP 2995)]
[New Thread 1094719824 (LWP 2989)]
[New Thread 1084229968 (LWP 2988)]
(no debugging symbols found)
0x0000003540a0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 142220

----------- .xsession-errors (6 sec old) ---------------------
(npviewer.bin:3012): Gdk-WARNING **: GdkWindow 0x3c00064 unexpectedly destroyed
(npviewer.bin:3012): Gdk-WARNING **: GdkWindow 0x3c00067 unexpectedly destroyed
(npviewer.bin:3012): Gdk-WARNING **: GdkWindow 0x3c00070 unexpectedly destroyed
The program 'npviewer.bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 1039 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
--------------------------------------------------