Closed Bug 334524 Opened 18 years ago Closed 18 years ago

Safe browsing extension triggers shutdown asserts

Categories

(Toolkit :: Safe Browsing, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Keywords: regression)

With safe browsing extension enabled, on shutdown I get:

###!!! ASSERTION: Event listener manager hash not empty at shutdown!: 'sEventListenerManagersHash.entryCount == 0', file ../../../../mozilla/content/base/src/nsContentUtils.cpp, line 642
###!!! ASSERTION: Using observer service after XPCOM shutdown!: 'Error', file ../../../mozilla/xpcom/ds/nsObserverService.cpp, line 140
###!!! ASSERTION: not an nsIRDFRemoteDataSource: 'remote != nsnull', file ../../../../mozilla/rdf/datasource/src/nsLocalStore.cpp, line 345

The second assert is from ~nsDownloadManager calling removeObserver after it's released in nsComponentManagerImpl::FreeServices.

The third assert is from LocalStoreImpl::Flush called by ~nsXULDocument (which is being released via GC after mozJSComponentLoader::UnloadModules.

None of these asserts are hit without safe-browsing.  At a guess, safe-browsing is getting the shutdown notification after layout, and it's holding on to layout things (like that nsXULDocument).
*** Bug 332591 has been marked as a duplicate of this bug. ***
Depends on: 332591
Flags: blocking1.9a2?
Keywords: regression
Flags: blocking1.9a2? → blocking-firefox3?
I removed the extension from CVS (bug 337336) so this should no longer be an
issus.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Flags: blocking-firefox3?
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.