crash drag & drop copying imap folders to different account [@ nsCOMPtr_base::~nsCOMPtr_base - nsDiskCacheStreamIO::Release] testing bug 448550. crash after attempting copy of 2 imap folders (both with small # messages) to different account, which resulted in error dialog "The current command did not succeed. The mail server responded:Missing or invalid argument to APPEND". both folders got created on target account, but only one message of only the first folder got copied. (copied empty local folders to imap copied fine.) bp-1d53b52c-e281-4427-ab20-c7d1f2090407 0 xpcom_core.dll nsCOMPtr_base::~nsCOMPtr_base objdir-tb/mozilla/xpcom/build/nsCOMPtr.cpp:81 1 thunderbird.exe nsImapMailCopyState::~nsImapMailCopyState mailnews/imap/src/nsImapMailFolder.cpp:7373 2 thunderbird.exe nsImapMailCopyState::`vector deleting destructor' 3 thunderbird.exe nsDiskCacheStreamIO::Release mailnews/imap/src/nsImapMailFolder.cpp:7376 4 xpcom_core.dll nsProxyReleaseEvent::Run objdir-tb/mozilla/xpcom/build/nsProxyRelease.cpp:52 5 xpcom_core.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:510 6 xpcom_core.dll NS_ProcessNextEvent_P objdir-tb/mozilla/xpcom/build/nsThreadUtils.cpp:227 7 thunderbird.exe nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:170 8 thunderbird.exe nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:192 9 thunderbird.exe XRE_main toolkit/xre/nsAppRunner.cpp:3279 10 thunderbird.exe NS_internal_main mail/app/nsMailApp.cpp:103 11 thunderbird.exe wmain toolkit/xre/nsWindowsWMain.cpp:87 12 thunderbird.exe __tmainCRTStartup objdir-tb/mozilla/memory/jemalloc/src/crtexe.c:591 13 kernel32.dll kernel32.dll@0x44910 Perhaps same issue as bug 457515 (Mac). And if related to nsImapMailCopyState / nsImapMailCopyState::`vector deleting destructor' see also bp-343e9bae-0638-468e-86a0-e30fb2090402 bp-7580417c-929d-442b-ae35-cacca2090401

if that stack is correct, it implies that somehow you got a message in the disk cache, and that we crashed trying to copy from the disk cache. It also sounds like the message might be a bit corrupted in the disk cache. A protocol log would be interesting.

don't know when I'll get to this :(

bug 610995 looks similar and I've not crashed again, so duping