From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; m18) Gecko/20001214 BuildID: 2000121404 Last few nightly builds I have installed on my system have crashed each time I close a Mozilla window. I get the following exception report from Windows: MOZILLA caused an invalid page fault in module APPCOMPS.DLL at 0157:6005ebd1. Registers: EAX=00000000 CS=0157 EIP=6005ebd1 EFLGS=00010246 EBX=00000000 SS=015f ESP=0068ea6c EBP=0068ea90 ECX=00000000 DS=015f ESI=018af130 FS=30ff EDX=0068ea84 ES=015f EDI=00000000 GS=0000 Bytes at CS:EIP: 8b 01 ff 76 1c ff 50 34 6a 00 8b f8 ff 75 f4 ff Stack dump: 0068ea84 00000000 006b0006 00000000 018b0928 00000000 0068eab0 00000000 00864854 0068eaa4 6005e51f 00000000 60d5167f 018af144 0068ebc4 60a3e051 APPCOMPS.dll is dated 14Dec00 5:28 PM Reproducible: Always Steps to Reproduce: Open Mozilla, close the browser window.

hello, i was using the linux nightly builds and exactly the same happens here but the only windows that are affected are opened BROWSER window. e.g. if you or some javascript opens more than one window and you close it. mozilla completely crash with an segfault. i thought that this got fixed with the 15-dec-2k release but well.. seems not ;)

*** Bug 62958 has been marked as a duplicate of this bug. ***

works-for-me on 2000121508 in Win2000.

Is this everytime you open and close the browser? Using a 2000121508 build I opened it up for the first time, then closed it, and it crashed. Subsequent closures were fine. Deleted all profile/registry data, and this behaviour repeated itself. Crashed only the first time. Using Win98 Confirming

changing platform to ALL as it is seen on Win95, Win98 and linux so far.

*** Bug 63099 has been marked as a duplicate of this bug. ***

I was having this problem wiht several of the releases last week, but today with the 2000121804 release the problem seems to have gone away.

I'm still getting this problem with build 2000121804. Doesn't happen with the chatzilla or the mailnews windows though, I noticed.

Eugene, can you please test this with a talkback build and report back with a TalkBack ID. thanks.

Ran the talkback build and it popped up a Netscape Quality Feedback panel. Is this what it's supposed to do? Sent in the report and the agent showed Incident ID TB23248562K. Hope this is what you need.

I just installed the latest nightly (Build ID 2000121904) and this problem seems to have disappeared on me. I can open and close as I please now. I'm not sure if this was resolved with the build, or if it might have been caused by a problem with my profile, which I wiped out and reconverted from my NS4.76 profile. Is anyone in a position to verify either the build or possible profile problem?

For 3-4 weeks on linux opt builds I've been seeing crashes when I exit the app, but I can close browser windows without crashing as long as they're not the only window (i.e. as long as the app doesn't try to exit). Filed bug 63230 on that, may or may not be related.

Seeing as you have filed bug 63230 and your other issue here has gone away, what would you like, this issue to be marked as a duplicate of bug 63230, to be marked WORKSFORME? :)

reporter's talkback looked like this. nsGlobalHistory::Commit [d:\builds\seamonkey\mozilla\xpfe\components\history\src\nsGlobalHistory.cpp, line 1852] nsGlobalHistory::Flush [d:\builds\seamonkey\mozilla\xpfe\components\history\src\nsGlobalHistory.cpp, line 1572] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 139] nsXPCWrappedNativeClass::CallWrappedMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativeclass.cpp, line 923] WrappedNative_CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 223] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 792] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2614] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 808] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 880] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3252] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 931] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 155] nsEventListenerManager::HandleEventSubType [d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line 844] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line 1427] GlobalWindowImpl::HandleDOMEvent [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 565] nsWebShell::FireUnloadEvent [d:\builds\seamonkey\mozilla\docshell\base\nsWebShell.cpp, line 263] nsWebShell::Destroy [d:\builds\seamonkey\mozilla\docshell\base\nsWebShell.cpp, line 1446] nsXULWindow::Destroy [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsXULWindow.cpp, line 330] nsWebShellWindow::Destroy [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 1783] nsWebShellWindow::Close [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 347] nsWebShellWindow::HandleEvent [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 436] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 691] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 708] nsWindow::DispatchStandardEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 729] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2833] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 944] KERNEL32.DLL + 0x35d9 (0xbff735d9) KERNEL32.DLL + 0x2222f (0xbff9222f) Is this still a bug?

I'm having the same problem on 2000122204-MTrunk (Win 98 System). Every time I close a browser window (any one), Mozilla crashes. A talkback report with the ID TB23457361W. I also believe this might be a dup of 62738. This really needs to be fixed. It has been an issue for a few weeks now. Thanks!

this is bug 62968 *** This bug has been marked as a duplicate of 62968 ***

brian@brianz.net: please attach your history.dat file to bug 62968. Thanks!

*** Bug 68808 has been marked as a duplicate of this bug. ***