9162 - crash on send. looks like when it tries to copy to the sent folder.

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

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

on linux, today build (july 1), crashes on send.

one pop account.  (that seems to matter.)

make sure you have a Sent folder.

here's the stack trace:
#0  0x40c73204 in CopyListener::OnStopCopy ()
#1  0x40663969 in nsMsgCopyService::ClearRequest ()
#2  0x40663c02 in nsMsgCopyService::DoNextCopy ()
#3  0x406639d2 in nsMsgCopyService::DoCopy ()
#4  0x4066416d in nsMsgCopyService::CopyFileMessage ()
#5  0x40c73466 in nsMsgCopy::DoCopy ()
#6  0x40c7335f in nsMsgCopy::StartCopyOperation ()
#7  0x40c710f3 in nsMsgComposeAndSend::StartMessageCopyOperation ()
#8  0x40c70ec9 in nsMsgComposeAndSend::MimeDoFCC ()
#9  0x40c6f954 in nsMsgComposeAndSend::DoFcc ()
#10 0x40c6f85c in nsMsgComposeAndSend::DoDeliveryExitProcessing ()
#11 0x40c6f881 in nsMsgComposeAndSend::DeliverAsMailExit ()
#12 0x40c6ef5e in MailDeliveryCallback ()
#13 0x40c75ec4 in nsMsgDeliveryListener::OnStopRunningUrl ()
#14 0x40656693 in nsUrlListenerManager::BroadcastChange ()
#15 0x406566e8 in nsUrlListenerManager::OnStopRunningUrl ()
#16 0x406828ef in nsMsgMailNewsUrl::SetUrlState ()
#17 0x40c6c55f in nsSmtpProtocol::ProcessProtocolState ()
#18 0x4068233c in nsMsgProtocol::OnDataAvailable ()
#19 0x400df1ef in nsStreamListenerProxy::OnDataAvailable ()
#20 0x400e2d94 in XP_FindContextOfType ()
#21 0x4009d9da in NET_GetMaxMemoryCacheSize ()
#22 0x4002451b in NET_FreeSocket ()
#23 0x400246c6 in NET_FreeSocket ()
#24 0x400bffb3 in NET_ProcessNet ()
#25 0x400c564b in NET_PollSockets ()
#26 0x400de17d in nsNetlibService::NetPollSocketsCallback ()
#27 0x401d925a in TimerImpl::FireTimeout ()
#28 0x401d958c in nsTimerExpired ()
#29 0x80e78cf in g_main_iteration ()
#30 0x80e6e54 in g_list_length ()
#31 0x80e72cf in g_list_length ()
#32 0x80e73e9 in g_main_iteration ()
#33 0x808530f in gtk_main ()
#34 0x40194fcf in nsAppShell::Run ()
#35 0x400fdc9a in nsAppShellService::Run ()
#36 0x80521ba in main ()

jefft landed some copy service code today. assigning to him.

I'm trying to build, debug and reproduce on my linux box to help jefft.

Comment 1

[jefft]

Accepting the bug. I cannot debug for the moment. The tree is horked badly.

Comment 2

[lchiang]

Upgrading severity.
Ninoschka will try this on other platforms.

Doesn't matter if it's html or plain text compose window.

1) Start Messenger
2) New msg
3) Address the message and enter a subject
4) Send. The message gets sent and the compose window closes.  But, you cannot
do any other action. A core dump will follow afterwards.

We should fix this for M8 since one account is the most popular.

Comment 3

[lchiang]

Ninoschka reproduces this problem on Win32 with the second time she sends a
message.  Her talkback report is not available yet.

Comment 4

[Ninoschka Baca]

1999070108M8: Win32/NT4

Incident ID: 10655395

I reproduced this problem again but this time it crashed the first time I
selected the Send Message button. The prefs50.js includes compose_html set to
True.

Call Stack:    (Signature = CopyListener::OnStopCopy a88f63f1)

CopyListener::OnStopCopy
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgCopy.cpp, line 89]
nsMsgCopyService::ClearRequest
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgCopyService.cpp, line 226]
nsMsgCopyService::DoNextCopy
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgCopyService.cpp, line 322]
nsMsgCopyService::DoCopy
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgCopyService.cpp, line 248]
nsMsgCopyService::CopyFileMessage
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsMsgCopyService.cpp, line 484]
nsMsgCopy::DoCopy
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgCopy.cpp, line 197]
nsMsgCopy::StartCopyOperation
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgCopy.cpp, line 163]
nsMsgComposeAndSend::StartMessageCopyOperation
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 2569]
nsMsgComposeAndSend::MimeDoFCC
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 2554]
nsMsgComposeAndSend::DoFcc
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 1582]
nsMsgComposeAndSend::DoDeliveryExitProcessing
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 1540]
nsMsgComposeAndSend::DeliverAsMailExit
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 1547]
MailDeliveryCallback
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgSend.cpp, line 1294]
nsMsgDeliveryListener::OnStopRunningUrl
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsMsgDeliveryListener.cpp,
line 79]
nsUrlListenerManager::BroadcastChange
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsUrlListenerManager.cpp, line
89]
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsUrlListenerManager.cpp, line
100]
nsMsgMailNewsUrl::SetUrlState
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgMailNewsUrl.cpp, line 130]
nsSmtpProtocol::ProcessProtocolState
[d:\builds\seamonkey\mozilla\mailnews\compose\src\nsSmtpProtocol.cpp, line 1409]
nsMsgProtocol::OnDataAvailable
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgProtocol.cpp, line 143]
nsStreamListenerProxy::OnDataAvailable
[d:\builds\seamonkey\mozilla\network\module\nsNetThread.cpp, line 817]
OnDataAvailableProxyEvent::HandleEvent
[d:\builds\seamonkey\mozilla\network\module\nsNetThread.cpp, line 634]
StreamListenerProxyEvent::HandlePLEvent
[d:\builds\seamonkey\mozilla\network\module\nsNetThread.cpp, line 474]
PL_HandleEvent [plevent.c, line 494]
PL_ProcessPendingEvents [plevent.c, line 455]
_md_EventReceiverProc [plevent.c, line 916]
USER32.dll + 0x1250 (0x77e71250)
nsappshell.dll + 0x1852 (0x01601852)
apprunner.exe + 0x22cf (0x004022cf)
KERNEL32.dll + 0x1b304 (0x77f1b304)

Comment 5

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

I've checked in a bunch of fixes so the crash doesn't happen.

I've sent the diffs to jefft for review.

but I don't think I fixed the problem.

I'll leave that to jefft.

but it shouldn't crash in tomorrows build.

Comment 6

[jefft]

This should be fixed by now.

Comment 7

[esther]

Using builds 1990707 on win95, linux, mac this is fixed.  Verified.