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

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Tracking, defect)

Description

[timeless]

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

[Matthias Versen [:Matti]]

*** Bug 181494 has been marked as a duplicate of this bug. ***

Comment 2

[Matthias Versen [:Matti]]

*** Bug 181496 has been marked as a duplicate of this bug. ***

Comment 3

[Matthias Versen [:Matti]]

*** Bug 181498 has been marked as a duplicate of this bug. ***

Comment 4

[Matthias Versen [:Matti]]

*** Bug 181500 has been marked as a duplicate of this bug. ***

Comment 5

[Matthias Versen [:Matti]]

*** Bug 181503 has been marked as a duplicate of this bug. ***

Comment 6

[Matthias Versen [:Matti]]

*** Bug 181505 has been marked as a duplicate of this bug. ***

Comment 7

[Matthias Versen [:Matti]]

*** Bug 181507 has been marked as a duplicate of this bug. ***

Comment 8

[Matthias Versen [:Matti]]

*** Bug 181509 has been marked as a duplicate of this bug. ***

Comment 9

[Matthias Versen [:Matti]]

*** Bug 181512 has been marked as a duplicate of this bug. ***

Comment 10

[BMO Automation]

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.