20020425 branch build on Wins NT 1. Trun off Turbo and restart 2. In the URL bar of the browser, type 'news://news.mozilla.org/netscape.public.test' and hit enter (on a new profile, with no current news servers) 3. Click OK to confirm that you like to subscribe to netscape.public.test 4. Account Wizard appears for New Account Setup 5. Enter INVALID (for example, XXX) Newsgroup Server and finish up setting 6. Confirm dialog shows up: Would you like to subscribe to netscape.public.test? 7. Click OK 8. Download Headers dlg shows up, click Download 9. ALert dlg: Failed to connent to server XXX. Click OK 10. Click on news.mozilla.org - XXX in the folder pane 11. Click on n.p.test (nerscape.public.test) under news.mozilla.org - XXX 12. Crash !

Incident ID 5619171 Stack Signature nsMsgKeySet::IsMember 51a989b7

--> Seth (who can actually fix this) cc:ing david. I swear I've seen this stack before, but I searched bugzilla and can't find an open or resolved/verified fixed bug.

nsMsgKeySet::IsMember [d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgKeySet.cpp, line 632] nsNewsDatabase::IsRead [d:\builds\seamonkey\mozilla\mailnews\db\msgdb\src\nsNewsDatabase.cpp, line 214] nsNewsDatabase::IsHeaderRead [d:\builds\seamonkey\mozilla\mailnews\db\msgdb\src\nsNewsDatabase.cpp, line 228] nsMsgDatabase::GetStatusFlags [d:\builds\seamonkey\mozilla\mailnews\db\msgdb\src\nsMsgDatabase.cpp, line 1608] nsMsgHdr::GetFlags [d:\builds\seamonkey\mozilla\mailnews\db\msgdb\src\nsMsgHdr.cpp, line 208] nsMsgThreadedDBView::ListThreadIds [d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgThreadedDBView.cpp, line 388] nsMsgThreadedDBView::InitThreadedView [d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgThreadedDBView.cpp, line 171] nsMsgThreadedDBView::Open [d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgThreadedDBView.cpp, line 95] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 106] XPCWrappedNative::CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 2027] XPC_WN_CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1267] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 790] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2746] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 806] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 881] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3414] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 1019] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182] nsEventListenerManager::HandleEventSubType [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1218] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1821] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3461] nsTreeSelection::FireOnSelectHandler [d:\builds\seamonkey\mozilla\layout\xul\base\src\tree\src\nsTreeSelection.cpp, line 738] nsTreeSelection::Select [d:\builds\seamonkey\mozilla\layout\xul\base\src\tree\src\nsTreeSelection.cpp, line 369] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 106] XPCWrappedNative::CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 2027] XPC_WN_CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1267] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 790] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2746] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 806] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 881] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3414] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 1019] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 182] nsXBLPrototypeHandler::ExecuteHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 447] DoMouse [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLMouseHandler.cpp, line 118] nsXBLMouseHandler::MouseDown [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLMouseHandler.cpp, line 124] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1307] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3461] PresShell::HandleEventInternal [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6105] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6023] nsViewManager::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2076] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 306] nsViewManager::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1887] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 83] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 869] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 886] nsWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4713] ChildWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4968] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3630] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 1131] USER32.dll + 0x124c (0x77e7124c) 0x004e0055

Stephen, this stack trace looks a lot like the one you get by selecting a newsgroup, removing the account, adding it back, and clicking on the same newsgroup - I fixed that on the trunk and branch yesterday : bug 127707 - can you still recreate this with today's build?

David, thanks (I _knew_ I had seen that crash's stack recently). Yes, a dup. *** This bug has been marked as a duplicate of 127707 ***

verified dup based on stack. If we see it again, I'll reopen/refile.