User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050804 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050804 Firefox/1.0+ I just had a crash, TB8127909K. After some talkback poking, I discovered that oldest talkback report is from 2005073111, and there are many crashes since then - with FF, TB and SM. http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=1&searchby=stacksig&match=contains&searchfor=+nsGlobalWindow%3A%3A%7EnsGlobalWindow+5e0fbd3a&vendor=All&product=All&platform=All&buildid=&sdate=&stime=&edate=&etime=&sortby=bbid Reproducible: Didn't try Steps to Reproduce: 1. Close a window Actual Results: Crash Expected Results: No crash

I had 3 crashes while closing Firefox in the last week. In this thread several crashes are mentioned: http://forums.mozillazine.org/viewtopic.php?t=300045&postdays=0&postorder=asc&postsperpage=15&start=30 Unfortunately most, if not all, differ.

Possible Split Window Fallout? Incident ID: 8127909 Stack Signature nsGlobalWindow::~nsGlobalWindow 5e0fbd3a Product ID FirefoxTrunk Build ID 2005080306 Trigger Time 2005-08-05 21:10:32.0 Platform Win32 Operating System Windows NT 5.0 build 2195 Module firefox.exe + (001430ee) URL visited User Comments Since Last Crash 37869 sec Total Uptime 37869 sec Trigger Reason Access violation Source File, Line No. c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 288 Stack Trace nsGlobalWindow::~nsGlobalWindow [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 288]

This seems like it very well might be split-window related. Has anyone been able to reproduce this on Windows? I have not seen it on mac. According to Jaime on irc, crashes seem to be coming from lines 295 and 288 nsGlobalWindow.cpp, possibly two different bugs.

Nominating to block as this stack is no. 7 on the firefox trunk top crashers. With a reasomable split between lines 295 and 288 nsGlobalWindow.cpp Talkback Comments suggest this occurs when closing the browser/tabs/windows

The last checkin for bug 296639 fixed this AFAICT.