Closed Bug 11757 Opened 25 years ago Closed 25 years ago

Messenger hangs up after a sending a message.

Categories

(MailNews Core :: Composition, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 7426

People

(Reporter: skasinathan, Assigned: mscott)

Details

Overview Description:  Messenger freezes after sending a message to an imap
account. The sending account is a pop account (qatest36) and the message is sent
to an imap account (qatest37). I have 5 accounts in my pref file and just 1
identity which is my pop account (qatest36).

Steps to Reproduce:
1. Start messenger using Task | Messenger.
2. Click on imap account inbox.
3. Click New Msg.
4. Compose a new msg to imap account (qatest37).
5. Click Send. The compose window closes. But Messenger freezes. Couldn't do
anything. Wnidows NT Task manager says "Not Responding" for both Messenger and
Apprunner.

Actual Results: Messenger freezes.

Expected Results:  I should be able to to all other operations and close
messenger.

Build Date & Platform Bug Found: 1999-08-11-09, Windows release build.

Additional Information:
1. In step5 of "Steps to Reproduce", whenever I click 'send' messenger freezes
(even the compose window that is open). Sometimes I could see this happening and
sometimes couldn't. If I wait for somemore time after freezing (15-20 seconds)
it crashes.
Severity: normal → critical
Assignee: ducarroz → sspitzer
Severity: critical → normal
Reassigning to Seth. CC'ing mscott and bienvenu.

The little stack trace I got when using VC++ dubugger.
NTDLL! 77f6829b()
KERNEL32! 77f04f41()
_PR_WaitCondVar(PRThread * 0x0b4047c0, PRCondVar * 0x0b4034c0, PRLock *
0x0b403570, unsigned int 1000000) line 175 + 23 bytes
PR_Wait(PRMonitor * 0x0b403620, unsigned int 1000000) line 155 + 29 bytes
nsImapProtocol::ImapThreadMainLoop() line 678 + 16 bytes
nsImapProtocol::ImapThreadMain(void * 0x0a533028) line 533
_PR_NativeRunThread(void * 0x0b4047c0) line 379 + 13 bytes
_threadstartex(void * 0x0b404610) line 212 + 13 bytes
KERNEL32! 77f04ee8()

The threads shows up like this.

ThreadID  Suspend  Priority  Location.

00000069  1   		9
00000086  1   		9     [NSwINDOW ::~NSwINDOW]
000000d0  1   		9     [_PR_WaitCondVar]
000000dd  1   		9     [_PR_WaitCondVar]
000000e0  1   		9
00000107  1   		9     [_PR_MD_PR_Poll]


If I wait for somemore time (20-60 seconds)with out doing anything after
messenger freezes, it crashes. Here is the stack trace from Talkback report.



nsStr::EnsureCapacity [d:\builds\seamonkey\mozilla\xpcom\ds\nsStr.cpp, line 231]
nsStr::GrowCapacity   [d:\builds\seamonkey\mozilla\xpcom\ds\nsStr.cpp, line 248]
nsStr::Append         [d:\builds\seamonkey\mozilla\xpcom\ds\nsStr.cpp, line 293]
nsString::Append  [d:\builds\seamonkey\mozilla\xpcom\ds\nsString2.cpp, line 918]
nsHTMLToTXTSinkStream::Write
[d:\builds\seamonkey\mozilla\htmlparser\src\nsHTMLToTXTSinkStream.cpp, line 574]
nsHTMLToTXTSinkStream::WriteWrapped
[d:\builds\seamonkey\mozilla\htmlparser\src\nsHTMLToTXTSinkStream.cpp, line 920]
nsHTMLToTXTSinkStream::AddLeaf
[d:\builds\seamonkey\mozilla\htmlparser\src\nsHTMLToTXTSinkStream.cpp, line 797]
nsXIFDTD::AddLeaf
[d:\builds\seamonkey\mozilla\htmlparser\src\nsXIFDTD.cpp, line 1514]
nsXIFDTD::HandleTextToken
[d:\builds\seamonkey\mozilla\htmlparser\src\nsXIFDTD.cpp, line 623]
XIFDispatchTokenHandler
[d:\builds\seamonkey\mozilla\htmlparser\src\nsXIFDTD.cpp, line 279]
CTokenHandler::operator()
[d:\builds\seamonkey\mozilla\htmlparser\src\nsTokenHandler.cpp, line 83]
nsXIFDTD::HandleToken
[d:\builds\seamonkey\mozilla\htmlparser\src\nsXIFDTD.cpp, line 539]
nsXIFDTD::BuildModel
[d:\builds\seamonkey\mozilla\htmlparser\src\nsXIFDTD.cpp, line 476]
nsParser::BuildModel
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 943]
nsParser::ResumeParse
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 888]
nsParser::Parse
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 772]
nsTextEncoder::EncodeToString
[d:\builds\seamonkey\mozilla\layout\base\src\nsDocumentEncoder.cpp, line 230]
nsHTMLEditor::OutputToString
[d:\builds\seamonkey\mozilla\editor\base\nsHTMLEditor.cpp, line 3204]
nsEditorShell::GetContentsAs
[d:\builds\seamonkey\mozilla\editor\base\nsEditorShell.cpp, line 1536]
nsMsgCompose::SendMsg
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgCompose.cpp, line 375]
XPTC_InvokeByIndex
[d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp,
line 135]
nsXPCWrappedNativeClass::CallWrappedMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativeclass.cpp,
line 512]
WrappedNative_CallMethod
[d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp,
line 125]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 655]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2229]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 675]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2229]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 675]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2229]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 675]
js_InternalCall
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 748]
JS_CallFunctionValue
[d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 2645]
nsJSEventListener::HandleEvent
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 98]
nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line
608]
RDFElementImpl::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsRDFElement.cpp, line 2363]
nsEventStateManager::CheckForAndDispatchClick
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line
736]
nsEventStateManager::PostHandleEvent
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line
262]
PresShell::HandleEvent
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 1886]
nsView::HandleEvent
[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 835]
nsViewManager::DispatchEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1611]
HandleEvent
[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 67]
nsWindow::DispatchEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 502]
nsWindow::DispatchWindowEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 523]
nsWindow::DispatchMouseEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3270]
ChildWindow::DispatchMouseEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3463]
nsWindow::ProcessMessage
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2526]
nsWindow::WindowProc
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 572]
USER32.dll + 0x1820 (0x77e71820)
Assignee: sspitzer → mscott
re-assigning to mscott.  this is his baby.
whew, Seth, I thought you'd gone soft in the head there.
nope, no fontenelle on my noggin.
Is this something we need to fix for M9? I tried this on NT and didn't see this.
according to davidb, its a hard bug to fix.

I don't see it either.  (I'm on nt 4.0, sp 3.)

to determine service pack, I did "control panel | Help | about windows NT"

suresh is on SP 5.  could that be part of the problem?
I have SP3 at work, and I still have the problem - with SP4 at home, I don't
have the problem. I don't think it's SP-related. It's very hard to fix - I have
no idea what the problem is, except that closing windows hangs until the imap
thread finishes, even though the window has nothing to do with imap.
I don't think we can fix it for m9...
Isn't this a duplicate of 7426????
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Yes.

*** This bug has been marked as a duplicate of 7426 ***
Status: RESOLVED → VERIFIED
Suresh, pls add any pertinent details from this bug to bug 7426. Thanks.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.