Closed
Bug 153001
Opened 23 years ago
Closed 12 years ago
Need a mechanism to unload plugin dlls safely
Categories
(Core Graveyard :: Plug-ins, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
mozilla1.3beta
People
(Reporter: serhunt, Assigned: peterlubczynski-bugs)
References
Details
(Whiteboard: [PL2:NA])
This bug can be considered an independent task or as an action item for the
future development work.
XPConnected plugins need some special treatment when we decide to shut them down
and unload their dlls from memory. XPCOM may have outstanding references to the
plugin scriptable object and currently we don't have a reliable way to determine
when all plugin related ref counts get down to zero and the dll can be unloaded.
I think there can be different approaches to address the issue, we can probably
briefly exchange ideas here.
Updated•23 years ago
|
Target Milestone: --- → mozilla1.2alpha
Comment 2•23 years ago
|
||
Only unload these plugins when XPCOM broadcasts the shutdown notification. Also
we need to ensure that developers of these plugins get the message that after
this notification all outstanding refereces to mozilla are invalid.
Updated•23 years ago
|
Whiteboard: [PL2:NA]
Target Milestone: mozilla1.2alpha → mozilla1.0.2
Updated•23 years ago
|
Target Milestone: mozilla1.0.2 → mozilla1.2alpha
Comment 4•22 years ago
|
||
moving to 1.3 beta, this should get resolved for 1.3
Target Milestone: mozilla1.3alpha → mozilla1.3beta
Target milestone should be changed, mozilla1.3beta was a long time ago.
Updated•15 years ago
|
QA Contact: shrir → plugins
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•