Version: 2.18.1

What were you doing when the application crashed?
After I followed Susana's instructions, and duplicated the original problem, I noticed that the bugzill/bug buddy tool said there were no debug symbols for yelp.  So I installed the yelp-debuginfo and tried double-clicking the xml file again.  It seemed to create thousands of pop-up windows more energetically this time. 

This is related to (the same bug) IDs 464111 and 463484

The code used to duplicate this "bug" is in 464111.  Please let me know if you need any more "help" from me.

Regards,
Ernest


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 463507456 vsize: 463507456 resident: 21577728 share: 12414976 rss: 21577728 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186427015 rtime: 34 utime: 31 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496424288 (LWP 5140)]
[New Thread 1084229968 (LWP 5141)]
0x00000034c660d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 153287

----------- .xsession-errors ---------------------
most likely the X server was shut down or you killed/destroyed
the application.
The application 'yelp' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'yelp' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'yelp' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Yelp-ERROR **: Message did not receive a reply (timeout by message bus)
aborting...
--------------------------------------------------