Closed
Bug 234842
Opened 21 years ago
Closed 21 years ago
scary deadlock assertions exiting mozilla after referencing nsInstallTrigger
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: danm.moz, Assigned: jst)
Details
When exiting Mozilla I get a scary-sounding "potential deadlock" assertion. This
happens reliably after visiting a page referencing InstallTrigger, and only
after checking out the new nsInstallTrigger.cpp, checked in to fix bug 233953.
See the test page for that bug,
http://bugzilla.mozilla.org/attachment.cgi?id=141192&action=view , for a
convenient InstallTrigger visit.
On exit I get two of these:
###!!! ASSERTION: Potential deadlock between
nsComponentManagerImplMonitor@2afdd8 and Lock@2955610:
'Error', file d:/build/moz/mozilla/xpcom/threads/nsAutoLock.cpp, line 299
while in the nsCacheEntryDescriptor dtor. And sometimes I also get this
NS_ASSERTION(gManager, "Global Thread Manager is null!");
here:
handleTimerEvent(TimerEventType * 0x02f871f8) line 440 + 34 bytes
PL_HandleEvent(PLEvent * 0x02f871f8) line 671 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00d90258) line 606 + 9 bytes
nsEventQueueImpl::ProcessPendingEvents(nsEventQueueImpl * const 0x00d901a8) line
391 + 12 bytes
NS_ShutdownXPCOM(nsIServiceManager * 0x00000000) line 750
| Assignee | ||
Comment 1•21 years ago
|
||
FWIW, I see these assertions on exit w/o ever touching nsInstallTrigger.
And now I'm not getting them at all, whether I visit InstallTrigger or not. Must
have been some screwy, temporary thing. Closing.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•