Tilted Forum Project Discussion Community - Can someone decipher this Firefox leak report?

- Tilted Technology (https://thetfp.com/tfp/tilted-technology/)

- - Can someone decipher this Firefox leak report? (https://thetfp.com/tfp/tilted-technology/105257-can-someone-decipher-firefox-leak-report.html)

Can someone decipher this Firefox leak report?

After getting frustrated with Firefox memory leaks, I got this extension that claims to be a leak monitor. I just recently closed a tab and it reported this:

Code:

[+] [leaked object] (48792d0, http://forums.animesuki.com/clientscript/vbulletin_textedit.js, 2838-2873) = function (e) {

    if (e.ctrlKey) {

        switch (String.fromCharCode(e.charCode).toLowerCase()) {

          case "b":

            cmd = "bold";

            break;

          case "i":

            cmd = "italic";

            break;

          case "u":

            cmd = "underline";

            break;

          default:

            return;

        }

        e.preventDefault();

        vB_Editor[this.editorid].apply_format(cmd, false, null);

        return false;

    } else {

        if (e.keyCode == 9) {

            var firsticon = fetch_object("rb_iconid_0");

            if (firsticon != null) {

                firsticon.focus();

            } else {

                if (fetch_object(this.editorid + "_save") != null) {

                    fetch_object(this.editorid + "_save").focus();

                } else {

                    if (fetch_object("qr_submit") != null) {

                        fetch_object("qr_submit").focus();

                    } else {

                        return;

                    }

                }

            }

            e.preventDefault();

        }

    }

}

 [ ] prototype (1f2e658) = [object Object]

Can anyone tell me what this means? How is this object leaked? Can this be the source of my Firefox memory problems? Or are these not the droids I'm looking for?

Thank you...

Glancing at the code and Bugzilla it looks like a leak in FF's js code dealing with events. Seems to be new with 1.5. If an event is referenced by something from the document its instance counters increment artificially. (or increment without anyone claiming responsibility to decrement.) The object is never destroyed until close which is where Leak Monitor flags it. The js code could work around it but shouldn't need to. It's really a FF thing. Have you tried this with 1.5.0.4? Not much else you can do but try a nightly build. (looks like the fixes are in flux.)

Leak monitor doesn't know enough to tell where the problems lie. Good to make sure your extensions behave, or to home in on FF bugs, but most users would be doing chicken-blinks.

Unfortunately, I am running 1.5.0.4. Damn it! Firefox is a really good browser but these memory leaks are really pissing me off...

Try one of the nightlies.

http://ftp.mozilla.org/pub/mozilla.o...zilla1.8-l10n/
or
http://ftp.mozilla.org/pub/mozilla.o.../latest-trunk/

Might want to use a virtual machine. :)

Don't use the current Bon Echo nightlies (i.e., Firefox 2.0a), from the one released Monday to now. There's a wicked nasty crash bug. For many people, it is completely unusable right now. If you are interested in nightlies, wait for Bug 339861
crash since 20060530 hourly on the Firefox 2 branch [@ ntdll.dll] to be resolved. Or just get the 2.0a3 release, which just barely predates the checkin that caused this bug.