54050 - nsComponentManagerImpl::Shutdown can't work the way it is written

Status: RESOLVED WONTFIX

(Core :: XPCOM, defect, P3)

Description

[Jon Smirl]

nsComponentManagerImpl::Shutdown can't work the way it is written if nsDll is 
allowed to unload the libraries from memory.

1) nsComponentManagerImpl::Shutdown requires NSPR to be active in order to run.
2) nsComponentManagerImpl::Shutdown releases the component dlls from memory
3) When PR_Cleanup runs it calls things like the xpconnect dtor. The code for 
this dtor lives in a lib nsComponentManagerImpl::Shutdown unloaded from memory.

To fix this nsComponentManagerImpl::Shutdown need to be broken down into a two 
step process allowing PR_Cleanup to be run between the steps. Step one does 
everything except unload the libraries. Step two unloads the libraries and only 
uses static NSPR functions.

Comment 1

[Jon Smirl]

The general solution to this requires a change to NSPR, see bug 54189. If 54189 
is implemented nsComponentManagerImpl::Shutdown() can be left as is.

The only loader that currently experiences this shutdown problem is XPConnect. 
Bug 54264 is a fix to allow it to work without 54050 or 54189 being fixed.

Comment 2

[Asa Dotzler [:asa]]

setting Jon Smirl's bugs to New

Comment 3

[Ray Whitmer]

Transferring to default XPCOM owner.

Comment 4

[Asa Dotzler [:asa]]

reasigning warren bugs to default component owners.

Comment 5

[Doug Turner (:dougt)]

reassign all kandrot xpcom bug.

Comment 6

[Judson Valeski]

per discussion w/ dougt, topembed minusing this bug.

Comment 7

[Benjamin Smedberg]

components are responsible for cleaning up their TLS before unloading, and XPConnect is now doing that correctly. WONTFIX