I open my IMAP inbox, select a message, click reply (get an html compose window regardless of what my pref is set to -- separate bug), dismiss the compose window by clicking on the "x", and the app crashes: #0 0x40ef03df in nsGenericHTMLContainerElement::~nsGenericHTMLContainerElement (this=0x8bd88b4, __in_chrg=2) at nsGenericHTMLElement.cpp:2400 #1 0x40f4d58a in nsHTMLQuoteElement::~nsHTMLQuoteElement (this=0x8bd88a0, __in_chrg=3) at nsHTMLQuoteElement.cpp:99 #2 0x40f4d692 in nsHTMLQuoteElement::Release (this=0x8bd88a0) at nsHTMLQuoteElement.cpp:104 #3 0x40ef03e3 in nsGenericHTMLContainerElement::~nsGenericHTMLContainerElement (this=0x8985ac4, __in_chrg=2) at nsGenericHTMLElement.cpp:2400 #4 0x40efe9bc in nsBodyInner::~nsBodyInner (this=0x8985ac4, __in_chrg=2) at nsHTMLBodyElement.cpp:141 #5 0x40effb96 in nsHTMLBodyElement::~nsHTMLBodyElement (this=0x8985ab0, __in_chrg=3) at nsHTMLBodyElement.cpp:576 #6 0x40effca2 in nsHTMLBodyElement::Release (this=0x8985ab0) at nsHTMLBodyElement.cpp:581 #7 0x40ef03e3 in nsGenericHTMLContainerElement::~nsGenericHTMLContainerElement (this=0x8b85584, __in_chrg=2) at nsGenericHTMLElement.cpp:2400 #8 0x40f1f12e in nsHTMLHtmlElement::~nsHTMLHtmlElement (this=0x8b85570, __in_chrg=3) at nsHTMLHtmlElement.cpp:103 #9 0x40f1f232 in nsHTMLHtmlElement::Release (this=0x8b85570) at nsHTMLHtmlElement.cpp:108 #10 0x410e966d in nsCOMPtr<nsIContent>::assign_with_AddRef (this=0x411d8090, rawPtr=0x8550bbc) at ../../../dist/include/nsCOMPtr.h:745 #11 0x410ea329 in nsCOMPtr<nsIContent>::operator= (this=0x411d8090, rhs=@0xbfffe13c) at ../../../dist/include/nsCOMPtr.h:481 #12 0x40e83f58 in nsEventStateManager::PreHandleEvent (this=0x8942df8, aPresContext=@0x890c158, aEvent=0xbfffe52c, aTargetFrame=0x893cfb0, aStatus=@0xbfffe454, aView=0x893cb30) at nsEventStateManager.cpp:266 #13 0x40ed2f85 in PresShell::HandleEvent (this=0x89268e8, aView=0x893cb30, aEvent=0xbfffe52c, aEventStatus=@0xbfffe454) at nsPresShell.cpp:2398 #14 0x41311ec9 in nsView::HandleEvent (this=0x893cb30, event=0xbfffe52c, aEventFlags=8, aStatus=@0xbfffe454, aHandled=@0xbfffe3f8) at nsView.cpp:839 #15 0x41311e5d in nsView::HandleEvent (this=0x893b0a0, event=0xbfffe52c, aEventFlags=8, aStatus=@0xbfffe454, aHandled=@0xbfffe3f8) at nsView.cpp:823 #16 0x41311e5d in nsView::HandleEvent (this=0x893afe8, event=0xbfffe52c, aEventFlags=8, aStatus=@0xbfffe454, aHandled=@0xbfffe3f8) at nsView.cpp:823 #17 0x41311e5d in nsView::HandleEvent (this=0x892a890, event=0xbfffe52c, aEventFlags=28, aStatus=@0xbfffe454, aHandled=@0xbfffe3f8) at nsView.cpp:823 #18 0x4131dbe3 in nsViewManager::DispatchEvent (this=0x8926370, aEvent=0xbfffe52c, aStatus=@0xbfffe454) at nsViewManager.cpp:1722 #19 0x4130ffe4 in HandleEvent (aEvent=0xbfffe52c) at nsView.cpp:68 #20 0x405f5dcb in nsWidget::DispatchEvent (this=0x8926578, aEvent=0xbfffe52c, aStatus=@0xbfffe4f0) at nsWidget.cpp:1386 #21 0x405f59fc in nsWidget::DispatchWindowEvent (this=0x8926578, event=0xbfffe52c) at nsWidget.cpp:1277 #22 0x405f5aa4 in nsWidget::DispatchFocus (this=0x8926578, aEvent=@0xbfffe52c) at nsWidget.cpp:1299 #23 0x405fa8e0 in nsWindow::SetFocus (this=0x8926578) at nsWindow.cpp:634 #24 0x4041a37f in GlobalWindowImpl::Focus (this=0x8909f48) at nsGlobalWindow.cpp:1252 #25 0x403acea0 in nsWebShellWindow::HandleEvent (aEvent=0xbfffe6ec) at nsWebShellWindow.cpp:559 #26 0x405f5dcb in nsWidget::DispatchEvent (this=0x81b2568, aEvent=0xbfffe6ec, aStatus=@0xbfffe6a4) at nsWidget.cpp:1386 #27 0x405f59fc in nsWidget::DispatchWindowEvent (this=0x81b2568, event=0xbfffe6ec) at nsWidget.cpp:1277 #28 0x405f5aa4 in nsWidget::DispatchFocus (this=0x81b2568, aEvent=@0xbfffe6ec) at nsWidget.cpp:1299 #29 0x405faa2e in nsWindow::OnFocusInSignal (this=0x81b2568, aGdkFocusEvent=0xbfffeac8) at nsWindow.cpp:700 #30 0x405f822a in nsWidget::FocusInSignal (aWidget=0x81b26d0, aGdkFocusEvent=0xbfffeac8, aData=0x81b2568) at nsWidget.cpp:2549

I think this is the same as http://bugzilla.mozilla.org/show_bug.cgi?id=17937. Only occurs if you don't type anything in the compose window after you do a reply.

Right, same bug, same stack trace. definitively a dup... *** This bug has been marked as a duplicate of 17937 ***