Closed Bug 283199 Opened 19 years ago Closed 19 years ago

nsBrowserContentListener.js never unsets the parent content listener

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: bzbarsky, Unassigned)

Details

Docshells hold a weak ref to the parent content listener.  So the parent content
listener needs to be explicitly nulled out before it goes away (so before the
JSObject is destroyed).  Not doing that is generally a good way to have
intermittent crashes.

Note: I can't find a reasonable component for this, so dumping in general...
Don't need to unregister nsISupportsWeakReferences
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.