Closed
Bug 181494
Opened 22 years ago
Closed 22 years ago
mozilla xpcom objects should gracefully handle being created and destroyed w/o being used
Categories
(Core Graveyard :: Tracking, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 181491
People
(Reporter: timeless, Assigned: timeless)
Details
(Keywords: meta)
The concept is that each xpcom object's destructor should tolerate no methods
being called other than whatever happens when createInstance is called (normally
this is just the c++ constructor) before it is destroyed. xpcom has a facility
for an additional method to be called (no params, but it allows for an object to
try to allocate memory, fail, and return an xpcom error which is converted into
a createInstance failure and js exception if the caller is xpconnect).
|
||
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 181491 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
|
||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•