Closed Bug 243940 Opened 21 years ago Closed 21 years ago

Mozilla crashes when sending email

Categories

(MailNews Core :: Composition, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 242768

People

(Reporter: db48x, Assigned: sspitzer)

Details

Whenever I send an email mozilla crashes. The email get's sent correctly, and put in the sent folder correctly. This is a build from about a week ago, I'm pulling the latest now. I've got a stack: #0 IM_get_input_context (aArea=0x0) at /home/db48x/moz/mozilla/widget/src/gtk2/nsWindow.cpp:4278 #1 0x41d9c7b3 in nsWindow::IMELoseFocus() (this=0xb12e510) at /home/db48x/moz/mozilla/widget/src/gtk2/nsWindow.cpp:3904 #2 0x41d9c715 in nsWindow::IMEDestroyContext() (this=0xb12e510) at /home/db48x/moz/mozilla/widget/src/gtk2/nsWindow.cpp:3875 #3 0x41d95608 in nsWindow::Destroy() (this=0xb12e510) at /home/db48x/moz/mozilla/widget/src/gtk2/nsWindow.cpp:367 #4 0x410e2d45 in ~nsView (this=0xadde520) at /home/db48x/moz/mozilla/view/src/nsView.cpp:151 #5 0x410e5b93 in ~nsViewManager (this=0xae57918) at nsViewManager.h:350 #6 0x410e5d3b in nsViewManager::Release() (this=0x0) at /home/db48x/moz/mozilla/view/src/nsViewManager.cpp:508 #7 0x08060755 in ~nsCOMPtr_base (this=0x0) at nsCOMPtr.cpp:81 #8 0x40f7cf5f in ~DocumentViewerImpl (this=0xae6b2d8) at nsPrintData.h:75 #9 0x40f7c953 in DocumentViewerImpl::Release() (this=0x0) at /home/db48x/moz/mozilla/content/base/src/nsDocumentViewer.cpp:513 #10 0x08060755 in ~nsCOMPtr_base (this=0x0) at nsCOMPtr.cpp:81 #11 0x410fc583 in GlobalWindowImpl::Close() (this=0x85c13b8) at /home/db48x/moz/mozilla/dom/src/base/nsGlobalWindow.cpp:2153 #12 0x40b3e58f in XPTC_InvokeByIndex () at /home/db48x/moz/mozilla/xpcom/reflect/xptcall/src/md/unix/xptcinvoke_gcc_x86_unix.cpp:65 #13 0x41228589 in XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) (ccx=@0xbfffe114, mode=182965288) at /home/db48x/moz/mozilla/js/src/xpconnect/src/xpcwrappednative.cpp:2026 #14 0x4122e5e6 in XPC_WN_CallMethod(JSContext*, JSObject*, unsigned, long*, long*) (cx=0x81d9400, obj=0x9456f30, argc=0, argv=0x0, vp=0xbfffe264) at /home/db48x/moz/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp:1287 #15 0x4004aeb6 in js_Invoke (cx=0x81d9400, argc=0, flags=0) at /home/db48x/moz/mozilla/js/src/jsinterp.c:1281 #16 0x40053fc8 in js_Interpret (cx=0x81d9400, result=0xbfffe5c0) at /home/db48x/moz/mozilla/js/src/jsinterp.c:3370 #17 0x4004af7a in js_Invoke (cx=0x81d9400, argc=4, flags=2) at /home/db48x/moz/mozilla/js/src/jsinterp.c:1301 #18 0x41223cf4 in nsXPCWrappedJSClass::CallMethod(nsXPCWrappedJS*, unsigned short, nsXPTMethodInfo const*, nsXPTCMiniVariant*) (this=0x8628018, wrapper=0x0, methodIndex=3, info=0x84ff110, nativeParams=0xbfffe954) at /home/db48x/moz/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:1336 #19 0x4122031d in nsXPCWrappedJS::CallMethod(unsigned short, nsXPTMethodInfo const*, nsXPTCMiniVariant*) ( this=0xae734a0, methodIndex=0, info=0x84ff110, params=0xbfffe954) at xpcprivate.h:2138 #20 0x40b3e6c1 in PrepareAndDispatch (methodIndex=3221219692, self=0xae734a0, args=0xbfffea08) at /home/db48x/moz/mozilla/xpcom/reflect/xptcall/src/md/unix/xptcstubs_gcc_x86_unix.cpp:100 #21 0x459d57c0 in nsMsgProgress::OnStateChange(nsIWebProgress*, nsIRequest*, unsigned, unsigned) (this=0xae2f230, aWebProgress=0x0, aRequest=0x0, aStateFlags=16, aStatus=0) at nsCOMPtr.h:710 #22 0x459d55a8 in nsMsgProgress::CloseProgressDialog(int) (this=0x0, forceClose=0) at /home/db48x/moz/mozilla/mailnews/base/src/nsMsgProgress.cpp:124 #23 0x45cf4f86 in nsMsgComposeSendListener::OnStopCopy(unsigned) (this=0xadeae38, aStatus=0) at nsCOMPtr.h:710 #24 0x45cce9c5 in nsMsgComposeAndSend::NotifyListenerOnStopCopy(unsigned) (this=0xaeb72e0, aStatus=0) at nsCOMPtr.h:710 #25 0x45cd6c3f in CopyListener::OnStopCopy(unsigned) (this=0xad9db48, aStatus=0) at nsCOMPtr.h:710 #26 0x459a9f24 in nsMsgCopyService::ClearRequest(nsCopyRequest*, unsigned) (this=0x45a0b498, aRequest=0x94c14f8, rv=0) at nsCOMPtr.h:710
Severity: normal → critical
can you attach your stack in bug 242768 as it's quite detailed ? *** This bug has been marked as a duplicate of 242768 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.