BUGS: 1.9.4.x Dev

[therube]

I'm real early in the looking, but maybe we can disregard any interaction with NoScript as I believe I'm seeing the same sort of spikes.

So let this go at this point & I'll have to dig further.

[therube]

Grrrrr. Now I'm even more confused.

So I open a different SeaMonkey 2 Profile, disable NoScript & MR Tech Toolkit (the only added in extensions).

I open a bunch of pages, forcibly trying to get my Mem Usage up. Also opened Chat.
And I start to see rhythmic spikes. I get Mem Usage up to +200MB, & the spikes continue.
So I think, well it is not NoScript, but something with the browser itself.

In all other tests, once these spikes started, then continued regardless of what windows were left opened.
And in the same way, with (extensions) installed, once I got to a certain point in Mem Usage, memory was not released upon closing windows. So I could be sitting there with only about:blank open, yet still using +200MB of memory.

But, this time, without extensions (NoScript & MR Tech) memory usage did drop. Further, so did these CPU spikes?

Memory went from 230 to 170 to 120 to 99 where it sits now with 1 window & 4 tabs open. And the spikes stopped.

So you tell me?
(Do a View Image for large timeline.)

[therube]

I'm baaaack.

OK. Started off by removing NoScript.
XP SP3, Intel 4300, "4" GB RAM (only ~3 available ...), close to 0 free disk space on C: (ok, 150 MB atm).
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090617 SeaMonkey/2.0b1pre

Open browser & start loading various pages
CPU activity & memory usage on the rise
When I hit ~300 MB Mem Usage, I walked away:

http://i39.tinypic.com/152e23l.jpg

I start getting periodic CPU spikes, albeit relatively minor, ~12% CPU
I let that sit & stew for a while:

http://i39.tinypic.com/50j94.jpg

Start randomly closing down windows/tabs
At the end, I've closed most, but left a few open
Mem Usage drops from 300 MB down to 150 MB
I let that sit & stew for a while:

http://i41.tinypic.com/flkb5t.jpg

At this point NO CPU spikes
I let that sit & stew for a while:

http://i44.tinypic.com/oj2dty.jpg

Finally I close all but one window
Mem Usage drops from 150 to 120
Then I open a new window (about:blank)
Close the other window (so now only about:blank is open)
Mem Usage drops from 120 to 110

Re-enable NoScript, restart SeaMonkey & here I am

So ... differences from before (before NoScript was installed, now NoScript is disabled):

Mem Usage does drop. Before Mem Usage stayed high.
CPU spikes minimized or eliminated. Before large spikes persisted.


So ... ... are we anywhere closer to OZ?

(no I did not try 360000 this time, but that, from before, looks not to be it. but perhaps something is happening?)


Extensions:

Code: Select all

Adblock Plus
Auto Copy
ChatZilla (part of SeaMonkey)
Console2
Copy URL+
DOM Inspector (part of SeaMonkey)
Fetch Text URL
FlashGot
Image Zoom (disabled)
JavaScript Debugger (part of SeaMonkey)
JSView
Live HTTP headers
Named anchors
NoScript
Nuke Anything Enhanced
SeaMonkey Debug & Q&A UI (part of SeaMonkey

During this run, the only change I made was to disable NoScript.


I have been running for some time now with javascript.options.jit.chrome;true.
<and just now turned off, so after the fact for all that has been done on this computer so far>

Appears the severity of the CPU spike varies with the Mem Usage.


Pictures came from Sysinternals Process Explorer.

[Tom T.]

XP SP3, Intel 4300, "4" MB RAM (only ~3 available ...),

Are you sure that that isn't 4 GB RAM?

Okay, a typo. Seriously:

close to 0 free disk space on C: (ok, 150 MB atm).

I've read many times that a nearly-full drive has multiple impacts on performance for multiple reasons -- no point in iterating them here. This may not be your direct problem in this case, but try deleting, offloading, or compressing old, little-used files; offloading your art gallery to a flash drive (you can get 8 GB for about $25 or less on sale, or maybe 16 GB by now), and you will be able to work with and view your art gallery just as easily from the flash drive. Burn the videos to DVD. Etc, etc.

FWIW, I have a 74.3 GB HD (what the marketers call "80 GB" in decimal measurement), and ATM, when first booted, it uses about 894 (binary) MB, leaving 73.4 GB, or about 98.3% of the drive, available. And WOW, is it fast! OK, that's a little extreme, but I have read that best performance is achieved with <= 50% HDD used.

For one thing, it's not possible to defrag your drive, because the defragger has no room to temporarily store files and fragments while it's cleaning up and putting them back together in one place. I would imagine the drive is badly fragmented.

All of this could make a significant difference in all performance issues.

[therube]

Yes, 4 GB (& now adjusted).

close to 0 free disk space on C: (ok, 150 MB atm).

True.
E: is my System Drive, & I have plenty of free space there. Other partitions too, some with space, others not.
Yes, I'm sure a nearly full drive (partition) will have an adverse affect on just about everything.
(Until I'm able to get myself a larger HDD, I have to make do with what I've got.)

[Giorgio Maone]

v 1.9.4.4
=====================================================================
+ Origin tracing speed and accuracy improvements
+ Enhanced frame busting emulation
+ Further DNS optimizations

[Tom T.]

(Until I'm able to get myself a larger HDD, I have to make do with what I've got.)

Or, as mentioned, clean up the garbage and the obsolete, burn CDs and DVDs (seen CDs and DVDs on sale at Radio Shack for about 14-16 cents each in bulk). $8.00 buys you 235 GB storage, which should be enough. Flash drives getting larger and cheaper by the minute, too. Heck, I'd use my 8GB Flash drive instead of a hard drive, if the motherboard could live with it (it won't).

[therube]

(my note taking is not too good. really should get a bigger scrap of paper.)

Starting from where I left off yesterday in an existing session (& so this would have been with 1.9.4.3) ...

NoScript enabled (ABE may or may not have been enabled, not sure?). Intel.

I was sitting at 430MB/20% (Mem Usage/periodic CPU spikes)
Opened more pages, 565MB/30%, & more, 578MB/40%
Start closing pages, 477MB/40%, on down to one single page, 419MB/30-40% still!?


Disable NoScript.

Load pages from history, including opening Chat, 650MB/25%



I start closing down windows, Chat too, & in the end I've dropped to, 133MB/0%
That is good!




Install 1.9.4.4.
(ABE is disabled. I must have disabled it somewhere along the line, just not sure when?)

I start loading various pages & also have Chat open, 169MB/16%
Close all pages except for one about:blank & Chat, 157MB/0% (spikes stopped, not much reduction in Mem Usage)


Renabled ABE & off again I go.

Worked my way back up to 615MB/30%

Now to start closing ... down to only this window, 432MB/40%

So appears (extensions) may inhibit the release of memory?
Not all is going to be related to extensions, but extensions seem to exacerbate the situation.
Once Mem Usage reaches certain levels, appears less likely to give back or give up.
"Spikes" increase as Mem Usage goes up, so you're hit with a double-wammy.

Does display of the Notification Bar "cost"?
On a page loaded in the background does Notification Bar "poll" waiting for page to go to foreground?
And in the same way do other aspects of extensions poll waiting for focus. And does it cost even though pages are in background?

[therube]

NoScript 1.9.4.4, SeaMonkey 1.1.17, Intel.
Within a short period of time, I racked up this, 1 GB .
(Also notice I did NOT see CPU spikes - this being different from what I saw in SeaMonkey 2.)

I then reverted back to NoScript 1.9.3.3 & saw nothing like that. I got Mem Usage up to around a max of 300 MB, & closing windows did release memory. Much more as expected. I'll have to revert back 10 1.9.3.3 in SeaMonkey 2 & see if my issues there also subside.

In both instances (1.9.4.4 & 1.9.3.3), this was just in general browsing. I was not specifically trying to force anything. Just going about what I would normally do. (Though I would tend to keep windows open rather then closing them, but only so that they would increase Mem Usage.)

[therube]

NoScript 1.9.4.4, SeaMonkey 2, Intel.
I get periodic CPU spikes (albeit relatively minor) even when Mem Usage is relatively low. And their magnitude seems to increase as Mem Usage increases.

[therube]

NoScript 1.9.3.3, SeaMonkey 2, Intel.
I still get periodic CPU spikes (~7%), though the magnitude is less even with Mem Usage being greater then the example above.
(Again, random sites, just general browsing & that's where I happen to be at the moment.)

[Giorgio Maone]

v 1.9.4.5
=====================================================================
x Further memory footprint and performance ABE optimizations

@therube:
those spikes are probably the Mozilla garbage collector at work (more memory to traverse/collect = more work).
Anyway I tried a dry run with Seamonkey 1.17 without NoScript, and I've observed it consistently leak on its own (for instance, Google Maps adds about 5-7 MB private bytes each visit and this memory is apparently never reclaimed back).

[therube]

While I don't doubt that, it appears that things are worse & to a large degree with the more recent builds.
SeaMonkey 1.1.17 looks to be behaving better then SeaMonkey 2.
Have not put in NoScript 1.9.4.5 yet.

More pictures following...

[therube]

Still with NoScript 1.9.3.3, SeaMonkey 2, Intel.

I've loaded more pages, doing more things, all kinds of windows & sites open.
Now up to around 330MB Mem Usage & 17% spikes. I had all kinds of stuff open. Much of the smaller spikes are likely pages "doing their thing" - animations, reloads, ... Typically in earlier runs I'd try to keep that kind of stuff to a minimum.



Now as I start closing down windows, Mem Useage is droppping.
With most (but not all) windows closed, I've dropped from 330MB to 210MB. Spikes have dropped from 17% to 7%.
(Expand this picture to more fully see the memory & spike drops. <might depend upon your browser how it looks>)



Behaving well. Better then with later builds.
1.9.3.3 takes longer to load up memory & it gives it back easier (more fully), while at the same time Spikes also become less extreme.
Again different from what I see in the #devs.

Not perfect, & the browser itself certainly will not be perfect, but in the case of SeaMonkey 2, with the #devs, it was to the point where browsing was being adversely affected. (I'm more apt to be bothered by such things when typing in forums as that is extremely noticeable.) With SeaMonkey 1.1.17, even at 1GB, I "knew" things weren't "right", but I was able to function relatively well. (Was doing no posting so that did not stand out.)

[GµårÐïåñ]

Ok, I am pissed specially that I took alot of time that I do not have trying to debug and find out why and nothing makes sense, simply NoScript isn't blocking squat like it should in the latest build, what the heck happened?

I go to a site, it shows its not allowed, so everything should be blocked based on my settings and yet the page is showing everything they are not supposed to be able to with NS enforced, so what's the point? This sucks.

My setting page:


But here is the page loading content from several off sites that are not allowed and do not show up in the list of sites to allow/disallow and the active content which I specifically want blocked and should be blocked if I have not allowed the site is just being allowed to load:


I am not happy at all, what's going on? And yes I have spent the last hour doing the "Standard Diagnostics" as well as a crap load of "non-Standard Diagnostics" including killing my entire profile and preferences and extensions and starting from scratch, Nada, nothing, zip.