Closed Bug 54050 Opened 24 years ago Closed 15 years ago

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

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: jonsmirl, Unassigned)

References

Details

(Keywords: topembed-)

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.
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.
Depends on: 54189
setting Jon Smirl's bugs to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
Transferring to default XPCOM owner.
Assignee: rayw → warren
reasigning warren bugs to default component owners.
Assignee: warren → kandrot
QA Contact: rayw → scc
reassign all kandrot xpcom bug.
Assignee: kandrot → dougt
Blocks: 98283
Target Milestone: --- → mozilla1.1
Target Milestone: mozilla1.1alpha → Future
Keywords: topembed+
per discussion w/ dougt, topembed minusing this bug.
Keywords: topembed+topembed-
Depends on: 316414
Assignee: dougt → nobody
QA Contact: scc → xpcom
components are responsible for cleaning up their TLS before unloading, and XPConnect is now doing that correctly. WONTFIX
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.