SeaMonkey Aurora Mem Usage Way High

[therube]

[orig, http://forums.informaction.com/viewtopi ... 079#p67079]
SeaMonkey Aurora (2.25a) Mem Usage Way High, compared to SeaMonkey 2.23 release
[this was with a Win7 system]

I noticed that (SeaMonkey) Aurora memory usage went to hell, so I went looking & the first thing I saw was YEINU: Your Experience Is Not Universal (even though it probably does not apply in my case .)

("Aurora is also using quite a bit more RAM then 2.23. 1.7 GB running 2.23 for a short while, then close down & doing nothing more reopen from Session Restore in Aurora, using 2.4 GB RAM.")


(And seeing, Performance regression: NS 2.6.8.7+ hogs memory on Fx 3.6, http://forums.informaction.com/viewtopi ... 10&t=18986, figured I see if reverting to an earlier NoScript in Aurora had any affect on my RAM usage, & it did not.)


And as it turns out, just yesterday on waking my computer from sleep, I said "so i left SeaMonkey running, put the computer to sleep, now that i'm back SeaMonkey is sitting there like a lump. can't interact with any windows. its not using any CPU or I/O. just sitting there.". (It did not crash, just hung, not to re-awaken.)

[therube]

[this is on an XP system]

223 was open for two days, doing all my normal work, & was using 975 MB RAM.
Quit.
Open 225, restoring Session & nothing more, & was using 1105 MB RAM.
Quit.
Open 223, restoring Session & nothing more, & was using 791 MB RAM.


Not that I know what this means...
(Note that NoScript is using ~3x more RAM in 225 vs 223)
[if i get time, i'll check that again, refreshing the page...]
The NoScript number dropped to 2.88 MB after a page refresh.

SM223:

http://oi41.tinypic.com/35d9is6.jpg

SM225

http://oi41.tinypic.com/rwtd7t.jpg

[therube]

FF "seamonkey-fied".
IOW, created a FF Profile & copied the following from SeaMonkey:

Code: Select all

01/17/2014  01:06 PM    <DIR>          ABE
01/17/2014  01:06 PM    <DIR>          adblockplus
01/17/2014  01:06 PM    <DIR>          chrome
01/17/2014  01:06 PM    <DIR>          extensions
01/17/2014  01:06 PM    <DIR>          plugins
01/17/2014  12:37 PM        41,943,040 places.sqlite
01/17/2014  12:37 PM            64,968 prefs.js
01/17/2014  12:37 PM         2,895,469 sessionstore.json
05/21/2012  10:16 AM             4,271 user.js

Doing nothing more then open FF, restore previous Session:

FF26 (akin SeaMonkey 2.23 release), using 725 MB RAM
FF28 (akin SeaMonkey 2.26 Aurora), using 1080 MB RAM

FF26

http://oi42.tinypic.com/23gzpg1.jpg

FF28

http://oi41.tinypic.com/16ib5ag.jpg

[therube]

To me, "Memshrink" ain't, currently.

[barbaz]

Note that NoScript is using ~3x more RAM in 225 vs 223

Same here with 2.26 vs 2.23.

The memory used by "SeaMonkey" seems enormous... it's only ~17-30 MB here. Total memory usage for Nightly as reported by system task monitor is ~140 MB.
Try disabling your extensions other than about:addons-memory, restarting SeaMonkey, doing session restore or whatever reproduced the memory hogging, and checking if the "SeaMonkey" entry in about:addons-memory shows significantly less memory usage.
If not, it might be worth filing a bug in Bugzilla?

[therube]

> Same here with 2.26 vs 2.23.

See my revision, above.
I didn't think initially to refresh the page after restoring from Session Restore, but after opening fully, then refreshing, NoScript's usage was about the same in each browser version.

> memory used by "SeaMonkey" seems enormous... it's only ~17-30 MB here

Yes, but then I do have an enormous number of windows/tabs (49/699) open.
So seeing RAM usage with those kinds of numbers is not out of the ordinary for me.


What is not ordinary, what is wrong, is the enormous amount of additional memory being used by Aurora as compared to release. (And I'm seeing that in both SeaMonkey & FF.) And at the same time, my UX has suffered in Aurora. (Slow context-menu operations...)


> it's only ~17-30 MB here

Likewise for me, in a different Profile with only 1 window & a dozen tabs.

> Try disabling your extensions other than...

I may or may not be able to even load without crashing (due to OOM) if I don't have NoScript installed? At the least I would need to have browser.sessionstore.max_concurrent_tabs;0 set.
(If I get time, I may give it a go?)

[barbaz]

What is not ordinary, what is wrong, is the enormous amount of additional memory being used by Aurora as compared to release. (And I'm seeing that in both SeaMonkey & FF.)

I know. This could still be extension-related, either if some Aurora-specific code in the extension is leaky/bad, or Aurora changed something in a way that happens to use a lot more memory than 2.23 and the extension author just needs to adapt.
Even if it is Aurora's problem, it's possible that the issue is only being exposed because of some extension.

I may or may not be able to even load without crashing (due to OOM) if I don't have NoScript installed?

Well I also have NS so that's unlikely to be the offender...
If you're risking crashing without NS, maybe try first with only NS and about:addons-memory?

[therube]

Since SeaMonkey Beta (for Windows, now) is finally out:

Win7
My regular, normal Profile, all extensions & whatnot
Doing nothing more then opening from Session Restore
79 Windows, 1290 tabs

Code: Select all

  SM 2.23  1500 MB
    FF 26  2121 MB
Beta 2.24  2488 MB
     2.25  2585 MB (old Aurora from 1-10-14)

Code: Select all

  SM 2.26  2589 MB (Nightly 2-1-14)
    FF 29  3376 MB (Nightly 1-31-14, 32-bit)
    FF 29  4583 MB (Nightly 2-1-14, 64-bit)

Oddly FF loaded plugin-container.exe (& Flash in x32 & FF26) & some "media" clip played in FF where no media content loads in SeaMonkey? (NoScript settings would be the same, but maybe there are diffs in SeaMonkey/FF & what they allow by default? And with NoScript piggy-backing on that?)

Also FF was always using CPU, variable, ~15% in Nightly, ~9% in FF26, where SeaMonkey would be using ~0%.

[barbaz]

@therube, where are you getting beta? I'd like to try it out (on Linux) but it's not even in the seamonkey release repository on ftp.mozilla.org...

[therube]

ftp://ftp.mozilla.org/pub/seamonkey/can ... tes/build2

(& I've added FF26 & FF29 x32 numbers above & some comments)

[barbaz]

Thanks. I'm actually getting pretty similar numbers (~140 MiB) between 2.23 and 2.24b with maybe 7 tabs open.
(2.24 seems to use slightly less memory than 2.23 here...)

How much additional memory is used if you have only about 5-10 tabs open?

Oddly FF loaded plugin-container.exe (& Flash in x32 & FF26) & some "media" clip played in FF where no media content loads in SeaMonkey? (NoScript settings would be the same, but maybe there are diffs in SeaMonkey/FF & what they allow by default? And with NoScript piggy-backing on that?)

Bug in NS? Probably worth mentioning on NoScript forum.

Also FF was always using CPU, variable, ~15% in Nightly, ~9% in FF26, where SeaMonkey would be using ~0%.

I see exactly the opposite on my (Mac & Linux) systems, Fx 18.0.2 vs SeaMonkey 2.20+...

[therube]

Through about:memory, I've attempted to "Load and diff..." two different saved runs, but that seems to fail, returning (essentially) nothing.

> Main Process (pid NNN)
> Explicit Allocations

(Each saved report is ~17 MB in size.)

[therube]

Got it .

It was a set of settings in my prefs.js causing the problem.
These two specifically:

> user_pref("layers.acceleration.disabled", true);
> user_pref("gfx.direct2d.disabled", true);

Bug 966662 - Memory usage increase with Firefox 26 compared to earlier
https://bugzilla.mozilla.org/show_bug.cgi?id=966662

[therube]

> Got it .


But not fully!
I can't seem to mitigate the issue on my XP system.

Bug updated.

[therube]

On my XP system, it seems to be "Azure" that caused its high memory usage:

> gfx.content.azure.enabled

When enabled (true), there is a large jump in memory usage.
When disabled (false), memory usage is essentially the same between SeaMonkey 2.23 & 2.24 (FF 26 & 27).