Possible [BUG] within Firefox browsers

[Marcoevich]

Dear community,

Something odd catched my eye last week.

Whenever I'm running Subsonic in a Firefox type browser (e.g. firefox or my default browser Palemoon), the browser is going to use more and more ram every hour!

I've contacted the Palemoon author, see: http://forum.palemoon.org/viewtopic.php?f=3&t=348, and we think Subsonic is causing a major javascript leak within the browser.

Also take a look at this: http://piclair.com/data/84802.jpg
http://piclair.com/data/abrer.jpg

Memory dump from about:memory:


├──1,645.98 MB (59.81%) -- js
│ ├────992.75 MB (36.07%) -- compartment(http://localhost:4040/login.view?)
│ │ ├──414.13 MB (15.05%) -- mjit-code
│ │ ├──343.92 MB (12.50%) -- gc-heap
│ │ │ ├──191.45 MB (06.96%) -- objects
│ │ │ ├──143.82 MB (05.23%) -- shapes
│ │ │ └────8.65 MB (00.31%) -- (4 omitted)
│ │ ├──154.12 MB (05.60%) -- scripts
│ │ ├───50.25 MB (01.83%) -- object-slots
│ │ ├───27.70 MB (01.01%) -- property-tables
│ │ └────2.63 MB (00.10%) -- (3 omitted)

As you can see, Subsonic is using almost 1gb(!!) of memory here. Where does this come from?
I've tested this with both Palemoon and Firefox browser, and they get really slow if they run with a subsonic tab open.

My question is: Where does the problem come from? Is it caused by subsonic or by the Firefox engine?
If you think it is the latter, please tell the guys at Mozilla about it. See the bugreport I opened there: https://bugzilla.mozilla.org/show_bug.cgi?id=710282

Subsonic is a great application If you can sort this out, even more people can enjoy subsonic without a hazzle.

Best regards,
Marcoevich

[BKKKPewsey]

FF version?
SS version?
OS ?

With 3 SS tabs open in FF 8 (1 login.view 1 playing video and 1 playing music) after 2 hrs total memory used was 198MB.
I do not know what is leaking but it isn't subsonic.

Perhaps you were playing a video of "Das BOOT"

[Marcoevich]

Firefox 8.0.1.
Palemoon 8.0
Subsonic 4.6
Windows 7 Ultimate X64

See, this is from today:

2,121.92 MB (100.0%) -- explicit
├──1,223.10 MB (57.64%) -- js
│ ├────807.42 MB (38.05%) -- compartment(http://localhost:4040/login.view;jsessio...)
│ │ ├──311.15 MB (14.66%) -- gc-heap
│ │ │ ├──172.01 MB (08.11%) -- objects
│ │ │ ├──129.23 MB (06.09%) -- shapes
│ │ │ └────9.92 MB (00.47%) -- (4 omitted)
│ │ ├──284.44 MB (13.40%) -- mjit-code
│ │ ├──138.44 MB (06.52%) -- scripts
│ │ ├───45.13 MB (02.13%) -- object-slots
│ │ ├───26.18 MB (01.23%) -- property-tables
│ │ └────2.08 MB (00.10%) -- (4 omitted)

I have only one tab of subsonic open and it is using 807 mb of memory..

Could it be leaking memory in combination with one of my plugins?

See the list of plugin's I use:

- Adblock Plus 1.3.10
- Adblock Plus Pop-up Addon 0.2.9
- Awesome screenshot: Capture and Annotate 2.3.3 (Disabled, Incompatible)
- Battlefield Play4Free 1.0.66.2 (Disabled)
- BetterPrivacy 1.67
- Cooliris 1.12.3.53363 (Disabled)
- Firebug 1.8.4
- Galaxytoolbar 2.6.6 (Disabled)
- Greasemonkey 0.9.13 (Disabled)
- IE Tab 2 (FF 3.6+) 3.10.7.2
- Lazarus: Form Recovery 2.3
- MAFIAAFire Redirector 0.9c
- Page Speed 1.12.0.1
- Pale Moon status bar 2.4
- Quick Translator 0.9 (Disabled)
- Session Manager 0.7.8.1
- SkipScreen 0.6.1.2
- Tab Counter 1.8.8
- UltraSurf Firefox Tool 2.0 (Disabled)
- Woordenboek Nederlands 3.0.1
- WOT 20111107

[tenzip]

Try disabling all your plugins. Then run SS for a while, check memory usage, and report back.

[BKKKPewsey]

This is possible however I have a number of the active plugin in your list in my set-up.
I would suggest try disabling the palemoon add-in.
Another one I would try is the Adblock extension.
I remember having an issue with that sometime ago but I cannot remember what it was now.

[Marcoevich]

@ Tenzip, BKKKPrewsey,

I've been running a fresh palemoon install on a fresh windows install in my VM. I can't see any increase in memory usage, so it must be one of my addons.
Also it is not the palemoon statusbar addon, since this one is by default enabled in any fresh installs.

I think I'm gonna disable my addons one by one to see which one is causing this leak. I'll report back here if and when I found the culprit

Thx for your suggestions!