From: tholen@antispam.ham   
      
   "Rich Walsh"  writes:   
      
   >> Just had a crash in XUL.DLL.  It was the kind of crash that used a   
   >> full-screen window to report the crash.  Naturally, I wasn't home   
   >> at the time the crash occurred, so the crash ended the energy-saving   
   >> standby mode for my dual-head monitors, allowing the static text to   
   >> burn in for possibly several hours.   
      
   > Full screen, like a kernel panic?   
      
   Full screen, yes, but after dismissing the dialog, the system returned   
   to the Desktop, and I was able to relaunch Firefox and continue,   
   whereas the kernel panics I've seen bring down the entire system,   
   forcing a reboot.  Also unlike a kernel panic in that the crash   
   had box-drawing characters around the two parts of the screen.  The   
   lower part had the usual three choices of dismissing the message,   
   seeing more detailed information, or showing just the message.   
      
   > I've never seen a mozapp cause one   
   > of those nor can I remember anyone reporting one.  Did you capture any   
   > of the info?   
      
   Sorry, no.  I mentally noted that the crash was in XUL.DLL, which   
   PSFILES reports as being associated with Firefox, and I recall   
   seeing something about session identifier 17 being involved.  But   
   I didn't copy down all the register information.   
      
   > In days of yore, the most common cause for these was the   
   > video driver.  What do you use?   
      
   SNAP build 420 from 2003 April 30 on a Matrox G450.  Dual head   
   1600x1200 monitors.   
      
      
   --- Internet Rex 2.31   
    * Origin: Aioe.org NNTP Server (1:261/20.999)