From 6f6cc8ed7e1488fdc2cf0ef0a91fe4b57b8d9b70 Mon Sep 17 00:00:00 2001 From: "mscott%netscape.com" Date: Thu, 7 Oct 1999 23:25:36 +0000 Subject: [PATCH] Bug #15615 --> when the proxy code is processing an event, we can't be holding onto the event queue's monitor. Because you could run into the scenario where in processing the event, the thread blocks waiting for an event from another thread. That thread tries to post the event to the orginal thread's event Queue but can't enter the queue's monitor. r=warren (or reviewed by me depending on your point of view since we figured it out together). --- xpcom/proxy/src/nsProxyEvent.cpp | 3 --- 1 file changed, 3 deletions(-) diff --git a/xpcom/proxy/src/nsProxyEvent.cpp b/xpcom/proxy/src/nsProxyEvent.cpp index 37923255d139..aaa2ab1ea804 100644 --- a/xpcom/proxy/src/nsProxyEvent.cpp +++ b/xpcom/proxy/src/nsProxyEvent.cpp @@ -467,8 +467,6 @@ void* EventHandler(PLEvent *self) return NULL; } - eventQ->EnterMonitor(); - // invoke the magic of xptc... nsresult rv = XPTC_InvokeByIndex( proxyObject->GetRealObject(), info->GetMethodIndex(), @@ -477,7 +475,6 @@ void* EventHandler(PLEvent *self) info->SetResult(rv); - eventQ->ExitMonitor(); } return NULL; }