27560 - Mail compose hangs with more than one address line

Status: VERIFIED DUPLICATE of bug 26618

(MailNews Core :: Composition, defect, P3)

Description

[Jim Roskind]

I'm not sure which complication of my sending an email reply is triggering the 
hang... but I can't even figure out how to work around it.  I'm running the 
optimized build from sweetlou, built/dated roughly 5:15pm Saturday afternoon.

To recreate:
a) Bring up mail
b) Pick a message to reply to (I chose the one to the hook this evening from 
mcafee about getting automated tests run).
c) Press reply
d) Composition window appears with mcafee in To: line
e) Click to focus in mcafee email address
f) Press "Enter" to move to next line
g) enter more than one email address (example: jevering, hamerly)
h) write complementary message about progress
i) Realize that you should have set the additional addresses as "CC".
j) Click on the "To:" dropdown next to jevering and hamerly
k) Mozilla windows freeeze, refuse to respond, and refuse to repaint :-(

Alternate approach to bug:
e) Click where the second "To:" pulldown should appear
f) Change to "CC"
g) enter several addresses (example: jevering, hamerly)
h) write complementary note to mcaffee in body
i) move mouse over the "send button"
j) press send (the system might already be hung... but it sure is hung now :-( )

I could try to go through all the other sequences of typing in the body, then 
doing addressing, and then *accidentally* giving focus to another application, 
and then seeing that mozilla was hung.

I could not get the message sent.

No work around... no glory... no positive feedback for good work... nada.

Sadly... no dogfood for me this evening.  I'll start trying the earlier 
(11:50am) build :-/.

Comment 1

[Jim Roskind]

Added dogfood keyword, and did some extra work on behalf of PDT to mark this 
baby PDT+ (so no one would wonder about its priority).

I'll try other builds now... to see if I can figure out when it happened.

Comment 2

[Jim Roskind]

I couldn't get a reply off in the 11:50am build either..

Maybe it is me.  It would be nice to at least hear that others are not seeing 
any of this, and that my machine is sick.

Comment 3

[(not reading, please use [e-mail] instead)]

when I try to reply, I get a bunch of asserts, and the message never sends

here's the stack trace to the assert:

NTDLL! 77f7629c()
nsDebug::Assertion(const char * 0x01f8eaa8, const char * 0x100a1310, const char 
* 0x01f8ea60, int 1074) line 189 + 13 bytes
nsDebug::NotReached(const char * 0x01f8eaa8, const char * 0x01f8ea60, int 1074) 
line 296 + 22 bytes
nsGenericHTMLElement::GetAttribute(int 0, nsIAtom * 0x01741450, nsString & 
{...}) line 1074 + 21 bytes
nsGenericHTMLContainerElement::BeginConvertToXIF(nsXIFConverter & {...}) line 
3013
nsHTMLTableCellElement::BeginConvertToXIF(const nsHTMLTableCellElement * const 
0x02c953b0, nsXIFConverter & {...}) line 112 + 18 bytes
nsDocument::BeginConvertToXIF(nsXIFConverter & {...}, nsIDOMNode * 0x02c953a4) 
line 2725
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x02c953a4) line 2793
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x046a64b0) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x046a64b0) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x0469b290) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x0469b290) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x04698d80) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x04698d80) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x046b66d0) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x046b66d0) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x046a9cb0) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x046a9cb0) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x0465b160) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x0465b160) line 2794
nsDocument::ConvertChildrenToXIF(nsXIFConverter & {...}, nsIDOMNode * 
0x0469cc90) line 2741 + 23 bytes
nsDocument::ToXIF(nsDocument * const 0x0469b6e0, nsXIFConverter & {...}, 
nsIDOMNode * 0x0469cc90) line 2794
nsDocument::CreateXIF(nsDocument * const 0x0469b6e0, nsString & {...}, 
nsIDOMSelection * 0x00000000) line 2834 + 26 bytes
nsTextEncoder::EncodeToString(nsTextEncoder * const 0x04799220, nsString & 
{...}) line 189
nsHTMLEditor::OutputToString(nsHTMLEditor * const 0x0467cca0, nsString & {...}, 
const nsString & {...}, unsigned int 0) line 4282 + 39 bytes
nsEditorShell::GetContentsAs(nsEditorShell * const 0x04680c00, const unsigned 
short * 0x047997f0, unsigned int 0, unsigned short * * 0x0012c968) line 2442 + 
53 bytes
nsMsgComposeAndSend::GetBodyFromEditor(nsMsgComposeAndSend * const 0x045f7ae0) 
line 1224
nsMsgComposeAndSend::ProcessMultipartRelated(int * 0x0012ce90, int * 0x0012cea0) 
line 1574 + 18 bytes
nsMsgComposeAndSend::HackAttachments(const nsMsgAttachmentData * 0x00000000, 
const nsMsgAttachedFile * 0x00000000) line 2054 + 16 bytes
nsMsgComposeAndSend::Init(nsIMsgIdentity * 0x03c64d10, nsMsgCompFields * 
0x045b0070, nsFileSpec * 0x00000000, int 0, int 0, int 0, nsIMessage * 
0x00000000, const char * 0x01afbc14, const char * 0x00000000, unsigned int 0, 
const nsMsgAttachmentData * 0x00000000, const nsMsgAttachedFile * 0x00000000) 
line 2514 + 16 bytes
nsMsgComposeAndSend::CreateAndSendMessage(nsMsgComposeAndSend * const 
0x045f7ae0, nsIEditorShell * 0x04680c00, nsIMsgIdentity * 0x03c64d10, 
nsIMsgCompFields * 0x045b0070, int 0, int 0, int 0, nsIMessage * 0x00000000, 
const char * 0x01afbc14, const char * 0x00000000, unsigned int 0, const 
nsMsgAttachmentData * 0x00000000, const nsMsgAttachedFile * 0x00000000, void * 
...) line 3320 +
nsMsgCompose::_SendMsg(int 0, nsIMsgIdentity * 0x03c64d10, const unsigned short 
* 0x00000000) line 618 + 137 bytes
nsMsgCompose::SendMsg(nsMsgCompose * const 0x045b0170, int 0, nsIMsgIdentity * 
0x03c64d10, const unsigned short * 0x00000000) line 704 + 20 bytes
XPTC_InvokeByIndex(nsISupports * 0x045b0170, unsigned int 7, unsigned int 3, 
nsXPTCVariant * 0x0012d4a4) line 139
nsXPCWrappedNativeClass::CallWrappedMethod(JSContext * 0x03c20bb0, 
nsXPCWrappedNative * 0x045b1950, const XPCNativeMemberDescriptor * 0x045b1b44, 
nsXPCWrappedNativeClass::CallMode CALL_METHOD, unsigned int 3, long * 
0x035a9294, long * 0x0012d664) line 898 + 43 bytes
WrappedNative_CallMethod(JSContext * 0x03c20bb0, JSObject * 0x0363fce0, unsigned 
int 3, long * 0x035a9294, long * 0x0012d664) line 200 + 34 bytes
js_Invoke(JSContext * 0x03c20bb0, unsigned int 3, unsigned int 0) line 665 + 26 
bytes
js_Interpret(JSContext * 0x03c20bb0, long * 0x0012df50) line 2292 + 15 bytes
js_Invoke(JSContext * 0x03c20bb0, unsigned int 1, unsigned int 0) line 681 + 13 
bytes
js_Interpret(JSContext * 0x03c20bb0, long * 0x0012e7f8) line 2292 + 15 bytes
js_Invoke(JSContext * 0x03c20bb0, unsigned int 0, unsigned int 0) line 681 + 13 
bytes
js_Interpret(JSContext * 0x03c20bb0, long * 0x0012f0a0) line 2292 + 15 bytes
js_Invoke(JSContext * 0x03c20bb0, unsigned int 1, unsigned int 2) line 681 + 13 
bytes
js_InternalInvoke(JSContext * 0x03c20bb0, JSObject * 0x029e5750, long 43931504, 
unsigned int 0, unsigned int 1, long * 0x0012f22c, long * 0x0012f1d8) line 754 + 
19 bytes
JS_CallFunctionValue(JSContext * 0x03c20bb0, JSObject * 0x029e5750, long 
43931504, unsigned int 1, long * 0x0012f22c, long * 0x0012f1d8) line 2787 + 31 
bytes
nsJSContext::CallEventHandler(nsJSContext * const 0x03c0f430, void * 0x029e5750, 
void * 0x029e5770, unsigned int 1, void * 0x0012f22c, int * 0x0012f228) line 562 
+ 33 bytes
nsJSEventListener::HandleEvent(nsIDOMEvent * 0x04792044) line 128 + 57 bytes
nsEventListenerManager::HandleEventSubType(nsListenerStruct * 0x044c6080, 
nsIDOMEvent * 0x04792044, unsigned int 4) line 677 + 19 bytes
nsEventListenerManager::HandleEvent(nsIPresContext * 0x041925d0, nsEvent * 
0x0012f75c, nsIDOMEvent * * 0x0012f724, unsigned int 7, nsEventStatus * 
0x0012fa20) line 817 + 25 bytes
nsXULElement::HandleDOMEvent(nsXULElement * const 0x044c61b0, nsIPresContext * 
0x041925d0, nsEvent * 0x0012f75c, nsIDOMEvent * * 0x0012f724, unsigned int 1, 
nsEventStatus * 0x0012fa20) line 2928
nsEventStateManager::CheckForAndDispatchClick(nsEventStateManager * const 
0x0459bc80, nsIPresContext * 0x041925d0, nsMouseEvent * 0x0012fb14, 
nsEventStatus * 0x0012fa20) line 1631 + 42 bytes
nsEventStateManager::PostHandleEvent(nsEventStateManager * const 0x0459bc80, 
nsIPresContext * 0x041925d0, nsGUIEvent * 0x0012fb14, nsIFrame * 0x035b27e8, 
nsEventStatus * 0x0012fa20, nsIView * 0x04196990) line 849 + 24 bytes
PresShell::HandleEvent(PresShell * const 0x04197e64, nsIView * 0x04196990, 
nsGUIEvent * 0x0012fb14, nsEventStatus * 0x0012fa20) line 2888 + 43 bytes
nsView::HandleEvent(nsView * const 0x04196990, nsGUIEvent * 0x0012fb14, unsigned 
int 28, nsEventStatus * 0x0012fa20, int & 0) line 799
nsViewManager::DispatchEvent(nsViewManager * const 0x04194320, nsGUIEvent * 
0x0012fb14, nsEventStatus * 0x0012fa20) line 1704
HandleEvent(nsGUIEvent * 0x0012fb14) line 69
nsWindow::DispatchEvent(nsWindow * const 0x04196874, nsGUIEvent * 0x0012fb14, 
nsEventStatus & nsEventStatus_eIgnore) line 493 + 10 bytes
nsWindow::DispatchWindowEvent(nsGUIEvent * 0x0012fb14) line 514
nsWindow::DispatchMouseEvent(unsigned int 301, nsPoint * 0x00000000) line 2932 + 
21 bytes
ChildWindow::DispatchMouseEvent(unsigned int 301, nsPoint * 0x00000000) line 
3150
nsWindow::ProcessMessage(unsigned int 514, unsigned int 0, long 3211281, long * 
0x0012fda0) line 2237 + 24 bytes
nsWindow::WindowProc(HWND__ * 0x002702e0, unsigned int 514, unsigned int 0, long 
3211281) line 673 + 27 bytes
USER32! 77e71820()
JS3250! 00310011()

Comment 4

[lchiang]

May be related to 26618?

Comment 5

[Richard Zach]

Just filed bug 27649: Reply and Reply-All doesn't set sender identity.  Is your
sender identity set?  If not, does the alternate approach work if you click on
the lone select widget button next to "From:"?  The rest looks to me like bug
26618, which hyatt marked a dupe of bug 26344 (hang on more than 2 addresses).

Comment 6

[Jim Roskind]

I strongly suspect this is a similar (but still unresolved) bug to the "hang 
when sending to several addresses" on a line (pointed out by Lisa as well).  
That bug was marked fixed... but I'm still having hangs in the Sunday night 
build.

I believe my "From:" field is "set," but yet it is currently not appearing when 
I do a reply.  Attempts to "set it" by clicking on the "From:" pop-down, causes 
a hang.  Attempts to check via the "Edit->Account" don't work, because in the 
sunday night build you can't get *ANY* menu under Edit or File in the mail app 
:-(.

We are falling short of catfood at this point :-/.

Fundamentally, this area has major problems right now, and I'm sure several 
"cute little bugs" are interacting to make the mail app unusable. 

Adding Hyatt to the cc list, since I think he indicated that he "fixed" the 
multiple address in To: line yesterday.

Hyatt: Have you tested/played with much of this stuff recently? 

Comment 7

[David Hyatt]

Works fine for me.  Tried all the tests in this bug.  NO hang.  Mail sent fine.

Comment 8

[Chris McAfee]

mail hangs on 2nd email address typed in, linux.

Comment 9

[Jean-Francois Ducarroz]

*** This bug has been marked as a duplicate of 26618 ***

Comment 10

[Jean-Francois Ducarroz]

As bug 26618 is marked as fixed but this bud still occurs, I am removing the duplicated resolution.

Comment 11

[Jean-Francois Ducarroz]

reassign to myself

Comment 12

[Richard Zach]

Getting a hang on Linux build 2000.02.14.09 when trying to enter second address
line or reply-all with more than one addresses.  Same symptoms as bug 26344.

Changing summary, platform = all.

Comment 13

[lchiang]

bug 26618 was reopened today, btw.

Comment 14

[Jean-Francois Ducarroz]

I wont be able to check this bug until bug 26618 is really fixed. It's maybe a 
dup of it!

Comment 15

[Phil Peterson]

This looks the same to me. I'm marking a dup.


*** This bug has been marked as a duplicate of 26618 ***

Comment 16

[lchiang]

I will mark verified as a duplicate.  other bug is still open.