11984 - [Dogfood] Sending & Replying to a plain text message causes a crash when clicking Send!

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect, P3)

Description

[Suresh]

Overview Description:  Replying to a plain text message causes a crash.

Steps to Reproduce:
1. Start messenger using Task | Messenger.
2. Compose and send a plain text message to yourself.
3. Do a Get Msg, Read that message.
4. Click 'Reply'. Type something in the body, Click send. It crashes.
   Note: Wait for sometime to see the crash.

The DOS Console displays the foll.
Created nsEditorShell
Created editorShell
### window.editorShell.wrapColumn exception text: Component returned failure cod
e: 0x8000ffff [nsIMsgCompose.wrapLength, {file: file:///D|/seamonkey/seamonkey_8
_16_99/x86rel/chrome/messengercompose/content/default/messengercompose.xul, line
: 148}] - failed
editor initialized in PLAIN TEXT mode
Attaching to WebShellWindow[]
Document: Done (0.06 secs)
JavaScript error: Package java defined twice ?


JavaScript error: onBoldChange is not defined


nsToolbarDragListener::MouseUp
SendMessage from XUL
GenericSendMessage from XUL
Looking for identity id3
Identity = [xpconnect wrapped nsIMsgIdentity]
GenerateAttachmentsString()
attachments =
GenerateAttachmentsString()
Looking for identity id3

The stack trace is:

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 1559]
nsMsgCompose::SendMsg
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgCompose.cpp, line 375]
XPTC_InvokeByIndex
[d:\builds\seamonkey\mozilla\xpcom\reflect\xptcal\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 3273]
ChildWindow::DispatchMouseEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3466]
nsWindow::ProcessMessage
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2529]
nsWindow::WindowProc
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 572]
USER32.dll + 0x1820 (0x77e71820)


Actual Results:  Crash !!

Expected Results: No Crash.

Build Date & Platform Bug Found:  1999-08-16-09-M9/ Windows NT 4.0

Additional Builds and Platforms Tested On:  Windows 98 (Esther).

Comment 1

[lchiang]

I just remembered. This is a duplicate of a bug that Peter entered.  I'll go
find it.

Comment 2

[lchiang]

Peter reported a similar bug http://bugzilla.mozilla.org/show_bug.cgi?id=11861.

Comment 3

[esther]

This also happens on a New Msg.  It passed the smoke test for windows because
but in both these cases for me, it crashes on the 2nd Send not the 1st send. I
will recheck linux now to see if I can get it to crash on multiple sends within
the same session, if so this will be on all OS.

Comment 4

[lchiang]

If possible, we'd like this fixed for M9.  Phil, can you target this bug with a
proper milestone? Thanks.

Comment 5

[esther]

Still happens with win32 build 1999082016 builds.

Comment 6

[Phil Peterson]

M10

Comment 7

[Suresh]

I am still seeing this problem in 1999-08-24-13-M9 build in Windows. This
happens sometimes while sending a New msg as well as Replying. So updating the
summary field to New Msg and Replying.

Comment 8

[Phil Peterson]

I marked this M10 because the smoke tests come out passing. Is this a smoke test
blocker? I'd prefer to avoid the M9 branch, but we'll go back if we have to.

Comment 9

[lchiang]

Jay's smoke tests passed because he tests using the default which is HTML
compose.

Here is the summary:

In M9, plain text compose on Win32 and Mac (see bug 11861) are not usable.  On
Win32, you will get a crash sometimes on the first send of a new message or
reply, but always crash on the second send of a new message or reply.  On Mac,
you will crash all the time sending plain text.

Comment 10

[Jean-Francois Ducarroz]

with a build from today, I have sent several new message and reply in plain text
and HTML mode without crashing. The only crash I get is when you reply to a
replied HTML message (bug 12334). Mark this bug as works for me.

Comment 11

[Suresh]

Ducarroz,  Are you using M9 build or M10 Build ?
FYI: This happens in M9 builds.

Comment 12

[Jean-Francois Ducarroz]

I am using a M10 debug build from this afternoon 2:30 pm

Comment 13

[lchiang]

If we accept this behavior for M9, then we will try this again in the latest M10
builds.  M9 has dragged on so long that I don't know if it's worth it to go back
and fix for M9.

Comment 14

[esther]

Using 19990923 build on win98 this worksforme too.  I will verify, it this comes
back we'll open a new bug.  Verified