90473 - Loading component in constructor eating memory.

Status: RESOLVED INCOMPLETE

(Core :: XBL, defect)

Description

[Aaron Kaluszka]

1. Install Jabberzilla.
2. Repeatedly click the Jabberzilla logo.
- Each click eats memory that is not recovered.
- Repeated fast clicking can crash browser. ("Memory could not be read")

Not sure if this is a Mozilla or Jabberzilla-only bug.
Win2K/Mozilla 2001071104-trunk/Jabberzilla beta 1 20010621

Comment 1

[Aaron Kaluszka]

Fast clicking also makes Mozilla use 100% CPU.

Comment 2

[Eric Murphy]

This is from a component loading in a binding constructor

<constructor>
var jabberXM = new Components.Constructor('@jabberxm.mozdev.org;1','JabberXM');
this.jabber = new jabberXM();
</constructor>

loading the binding, and therefore this constructor over and over is what's
eating the memory.

Great catch! Reassigning to Hyatt

Comment 3

[Eric Murphy]

David,

Am I supposed to be setting this.jabber = null in a <destructor> ?

Hopefully unloading a binding should automatically do this anyway, but maybe not.

Comment 4

[Olivier Cahagne]

do you still have the issue using latest 1.2 build and Jabberzilla version ?
http://ftp.mozilla.org/pub/mozilla/latest-1.2

Comment 5

[Eric Murphy]

This is an oldie...

To summarize, loading a component in an XBL constructor was eating memory. Not
sure if this is still doing it. If someone wants to test if the overall problem
is still there, feel free.

Comment 6

[Jesse Ruderman]

Sounds like "don't do that" material.  If you have a testcase that actually leaks, we'd like to see it.