Closed Bug 181491 Opened 22 years ago Closed 8 years ago

mozilla xpcom objects should gracefully handle being created and destroyed w/o being used

Categories

(Core Graveyard :: Tracking, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: timeless, Assigned: timeless)

References

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).
*** Bug 181494 has been marked as a duplicate of this bug. ***
*** Bug 181496 has been marked as a duplicate of this bug. ***
*** Bug 181498 has been marked as a duplicate of this bug. ***
*** Bug 181500 has been marked as a duplicate of this bug. ***
*** Bug 181503 has been marked as a duplicate of this bug. ***
*** Bug 181505 has been marked as a duplicate of this bug. ***
*** Bug 181507 has been marked as a duplicate of this bug. ***
*** Bug 181509 has been marked as a duplicate of this bug. ***
*** Bug 181512 has been marked as a duplicate of this bug. ***
Blocks: 181518
Blocks: 181519
No longer blocks: 181518
Depends on: 325386
Depends on: 325392
Depends on: 325395
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE. If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.