99362 - Crash on cancelling Send with Spell checker option on - Trunk & N620 [@ nsViewManager::ProcessPendingUpdates]

Status: VERIFIED DUPLICATE of bug 97664

(MailNews Core :: Composition, defect)

Description

[marina]

*** observed with 2001-09-12-03 0.9.4 build ****
Steps to reproduce:
- in Preferences  check " Spell messages before Send";
- compose a message, click Send;
- at this point the spell checker will come up;
- there is no way (unfortunately) to dismiss spell checker and go back to
message composition in order to change something. As soon as you close spell
checker the message is being sent. So if you want to cancel send you have to
click on the "cancel" on the message composition window. Do so and observe the
crash. When the spell checker is not on i don't see the crash on cancelling. And
one more detail, even though mozilla crash the cancelled message has been
sent.Track to follow

Comment 1

[marina]

here is a stack, incident ID #35289680
Stack Signature   nsViewManager::ProcessPendingUpdates 4b3d5b1d
Bug ID
Trigger Time 2001-09-12 09:17:45
Email Address [e-mail]
User Comments quitting send
Build ID 2001091205
Product ID Netscape6.20
Platform ID Win32
Trigger Reason Access violation
Stack Trace
nsViewManager::ProcessPendingUpdates
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1638]
nsViewManager::FlushPendingInvalidates
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 3829]
nsViewManager::ProcessInvalidateEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 3837]
nsInvalidateEvent::HandleEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 145]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072] 

Comment 2

[Andreas Becker]

Nominating for nsbranch and adding crash keyword.

Comment 3

[Scott MacGregor]

sounds like a nasty crasher. nsBranch+

Comment 4

[Scott MacGregor]

*** Bug 99469 has been marked as a duplicate of this bug. ***

Comment 5

[Jay Patel [:jay]]

Could this be related to bug 97664?  The stack signature for this crash is the
same as the one reported in that bug.  Sheela, can you take a look and see if
this is a dup?

Adding Trunk & N620 [@ nsViewManager::ProcessPendingUpdates] to summary for
tracking and also adding topcrash keyword.

Comment 6

[Sheela Ravindran]

As you said the stack trace is the same. I will mark this as dup.

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

Comment 7

[Sheela Ravindran]

verified as dup