Closed Bug 71799 Opened 24 years ago Closed 24 years ago

regxpcom issues some warnings & assertion fails

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
NetBSD
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: taya, Assigned: scc)

Details

regxpcom issues some warnings & assertion fails *** Registering nsAbSyncModule components (all right -- a generic module!) *** Registering nsTestDynamicModule components (all right -- a generic module!) *** Registering PSMComponent components (all right -- a generic module!) nsNativeComponentLoader: autoregistering succeeded *** Deferring registration of sample JS components registerSelf for remoteControl nNCL: registering deferred (0) *** Registering sample JS components nNCL: registering deferred (0) killing plugin host CanUnload_enumerate: skipping native *** Unloading sample JS components JS engine warning: 890 atoms remain after destroying the JSRuntime. These atoms may point to freed memory. Things reachable through them have not been finalized. ###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt == 0', file nsXPComInit.cpp, line 731 ###!!! Break: at file nsXPComInit.cpp, line 731 ###!!! ASSERTION: nsDOMEvent not thread-safe: 'owningThread == NS_CurrentThread ()', file nsDebug.cpp, line 488 ###!!! Break: at file nsDebug.cpp, line 488
Also linux(Red Hat 6.2) *** Registering nsTextImportModule components (all right -- a generic module!) *** Registering nsAbSyncModule components (all right -- a generic module!) *** Registering nsTestDynamicModule components (all right -- a generic module!) nsNativeComponentLoader: autoregistering succeeded *** Deferring registration of sample JS components registerSelf for remoteControl nNCL: registering deferred (0) *** Registering sample JS components nNCL: registering deferred (0) killing plugin host CanUnload_enumerate: skipping native *** Unloading sample JS components JS engine warning: 890 atoms remain after destroying the JSRuntime. These atoms may point to freed memory. Things reachable through them have not been finalized. ###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt == 0', file nsXPComInit.cpp, line 503 ###!!! Break: at file nsXPComInit.cpp, line 503 ###!!! ASSERTION: nsDOMEvent not thread-safe: 'owningThread == NS_CurrentThread()', file nsDebug.cpp, line 488 ###!!! Break: at file nsDebug.cpp, line 488
Reporter is this still a problem in the latest nightlies?
Marking WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.