Closed
Bug 11025
Opened 25 years ago
Closed 25 years ago
Crash after any IMAP copy operation
Categories
(MailNews Core :: Networking, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M9
People
(Reporter: rhp, Assigned: jefft)
References
Details
Hi guys,
I'm not sure who this really belongs to, but I've tried debugging it and I'm
kind of lost. Basically, we crash in the guts of XUL/JS on completion of an
IMAP copy operation. Local copies work fine. Just set your pref for fcc
operations to an Imap folder and you will see the problem. This pref is:
"mail.default_fcc_uri", "imap://rhp@parp.mcom.com/Sent"
Jeff, reassign this if it's out of your court, but I thought I would start with
you since I think JF is out of the office on vacation.
- rhp
Brendan, any idea what can casue this problem? Thanks, -- Jeff
JS_INLINE void
js_Lock(JSThinLock *p, jsword me)
{
JS_ASSERT(me == CurrentThreadId()); <===== assert here
if (js_CompareAndSwap(&p->owner, 0, me))
return;
if (Thin_RemoveWait(ReadWord(p->owner)) != me)
js_Enqueue(p, me);
#ifdef DEBUG
else
JS_ASSERT(0);
#endif
}
NTDLL! 77f7629c()
js_Lock(JSThinLock * 0x00cae554, long 10628512) line 577 + 39 bytes
js_AtomizeString(JSContext * 0x0c8db210, JSString * 0x0c6bfa68, unsigned int 3)
line 464 + 24 bytes
js_Atomize(JSContext * 0x0c8db210, const char * 0x0c9012d0, unsigned int 8,
unsigned int 0) line 523 + 19 bytes
LookupProperty(JSContext * 0x0c8db210, JSObject * 0x0bb715f8, const char *
0x0c9012d0, JSObject * * 0x0c6bfab4, JSProperty * * 0x0c6bfaac) line 1544 + 28
bytes
JS_LookupProperty(JSContext * 0x0c8db210, JSObject * 0x0bb715f8, const char *
0x0c9012d0, long * 0x0c6bfb10) line 1700 + 25 bytes
nsJSEventListener::HandleEvent(nsIDOMEvent * 0x0c902d60) line 80 + 28 bytes
nsEventListenerManager::HandleEvent(nsIPresContext & {...}, nsEvent *
0x0c6bfc9c, nsIDOMEvent * * 0x0c6bfc74, unsigned int 3, nsEventStatus &
nsEventStatus_eIgnore) line 958 + 21 bytes
GlobalWindowImpl::HandleDOMEvent(GlobalWindowImpl * const 0x0c8db3d4,
nsIPresContext & {...}, nsEvent * 0x0c6bfc9c, nsIDOMEvent * * 0x0c6bfc74,
unsigned int 1, nsEventStatus & nsEventStatus_eIgnore) line 2772
nsWebShell::Destroy(nsWebShell * const 0x0c8d5050) line 1093 + 34 bytes
nsWebShellWindow::Close(nsWebShellWindow * const 0x0c8d5660) line 441
nsMsgCompose::CloseWindow(nsMsgCompose * const 0x0cb281e0) line 520
nsMsgComposeSendListener::OnStopCopy(nsMsgComposeSendListener * const
0x0cb48fe4, unsigned int 0) line 1218
nsMsgComposeAndSend::NotifyListenersOnStopCopy(nsMsgComposeAndSend * const
0x0cb48200, unsigned int 0) line 2590
CopyListener::OnStopCopy(CopyListener * const 0x0cb4dd70, unsigned int 0) line
107
nsMsgCopyService::ClearRequest(nsCopyRequest * 0x0cb4dd10, unsigned int 0) line
228
nsMsgCopyService::NotifyCompletion(nsMsgCopyService * const 0x0cb4de40,
nsISupports * 0x0cb4a630, nsIMsgFolder * 0x0b71b81c, unsigned int 0) line 508
nsImapMailFolder::ClearCopyState(unsigned int 0) line 3294
nsImapMailFolder::OnStopRunningUrl(nsImapMailFolder * const 0x0b71b8b4, nsIURI *
0x0cb4db54, unsigned int 0) line 2577
nsUrlListenerManager::BroadcastChange(nsIURI * 0x0cb4db54, nsUrlNotifyType
nsUrlNotifyStopRunning, unsigned int 0) line 86
nsUrlListenerManager::OnStopRunningUrl(nsUrlListenerManager * const 0x0cb4da10,
nsIMsgMailNewsUrl * 0x0cb4db54, unsigned int 0) line 100
nsMsgMailNewsUrl::SetUrlState(nsMsgMailNewsUrl * const 0x0cb4db54, int 0,
unsigned int 0) line 109
nsImapProtocol::ProcessCurrentURL() line 894
nsImapProtocol::ImapThreadMainLoop() line 682
nsImapProtocol::ImapThreadMain(void * 0x00d2c660) line 532
_PR_NativeRunThread(void * 0x0c2ed730) line 379 + 13 bytes
_threadstartex(void * 0x0c2efdd0) line 212 + 13 bytes
KERNEL32! 77f04ee8()
Found the problem. nsMsgMailNewsUrl::SetUrlState() shouldn't be executed using
the imap thread. Needs to be proxied. Fix in hand waiting for tree to become
green.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Linux and Mac (1999-08-16-08 M9) and win_nt 4.0 (1999-08-16-09 M9)
IMAP: copy message to another folder works fine on all three platforms.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•