InformAction Forums

Unable to reproduce on 1.9.4.5, although on F2-20 and on XP. As you can see, (same page), everything is blocked as it should be.
Are you *sure* that the ABP site isn't in your Trusted list? Or try checking "Apply these restrictions to trusted sites too" as yours truly always does (then allow on per-site, per-use basis).

You can clearly see in the bottom right of the screenshot that it is not and that's why I included that. The fact is that whether reproducible or not, I am getting tired of "works fine for us, so it should for you" when I provide countless concrete evidence to show that it is indeed happening. For example, I mentioned how long ago that performance degrades? It took countless posts from therbue (who originally told me I was imagining it) to actually get any notice given to it. How many times I posted about the whitelist before finally Giorgio found out indeed I wasn't imaging it. What's the point of running the dev build, wasting countless hours resetting and doing this and that to test the damn thing if no one cares or listens to it unless someone else says its so.

IT IS HAPPENING, SIMPLE AS THAT. Hence why I include screenshots because obviously my word as a seasoned user of this addon isn't sufficient. Even though I don't have time to take a piss and need to allocate time to manage to get a break, I manage to post these things because through my day, they affect me and if I am to be simply ignored, then I might as well not do any testing and just wait for others to bitch and moan to get things fixed.

G, chill, Bro. I know you're having a bad day, week, month, etc., but the fact that I couldn't reproduce the issue is NOT in any way disparaging you or saying that you imagined the whole thing. It's simply a report from another user, and as noted, on a *different operating system* and, most important, *an older and deprecated version of Fx". I thought it was a positive contribution, to report my experience, but if it's perceived as a negative, I won't respond any more unless I can in fact reproduce the issue.

You're right that I overlooked the "Untrusted" in the menu, so I'm having a bad night too (about to call it quits), and it was a useless thing to say. I just wanted to contribute that I couldn't reproduce it.

You have other things on your mind right now. Go back to stable 1.9.3.3. for a few days, and when your plate has been cleaned a bit, c'mon back. Take care, Brother.

Just to close this part of the discussion, appears it was another extension (LocalRodeo) causing problems. See, 1.9.4.5 is Possibly Breaking ABP.

NoScript 1.9.4.5, SeaMonkey 1.1.17, AMD.

Simply opening stuff I would normally open. Doing nothing special.

Mem Usage gets up to 330MB. CPU is all over the place even after I stopped interacting with the browser. Doesn't seem to be particularly affecting me, though I do "notice" when I alt+tab between windows/applications. By the end of the graph, I've closed all windows except for a sole about:blank. Mem Useage has only dropped to 300MB. No CPU usage per say (except for a few % "hum"?).



Continuation of same graph. Mem Usage still unchanged. No spikes, which seems to be "normal" for SeaMonkey 1.1.17.

http://i41.tinypic.com/2qc11xt.jpg

I'll revert to NoScript 1.9.3.3 & see what gives.

(Reverted to) NoScript 1.9.3.3, SeaMonkey 1.1.17, AMD.

Pretty much went through (today's) history & opened EVERYTHING back up. Mem Usage going up & up. CPU through the roof. All to be expected.

http://i40.tinypic.com/5yw0fb.jpg

Took quite a while before CPU finally dropped & I could start doing things again .

http://i42.tinypic.com/2mqka48.jpg

Right now I sitting I'm sitting at 350MB & minimal CPU.
I'll run it for a while & then start closing windows & see what happens.

I've closed a LOT, but still have a LOT open.

Mem Usage has dropped from 350MB to 245MB.

Closing more & now I'm at 200MB. I've got 3 windows/16 tabs open.
Interestingly, as I've now opened some new windows, Mem Usage has actually dropped to 170MB. And as I open more, I've gone back up to 190MB.

... edits (additions) to come ...

Same session as above, NoScript 1.9.3.3, AMD.

About ready to close down. I'm left with 3 tabs open.
Didn't do a whole lot today, didn't try to force anything, just doing what I needed to do.
At the start of close, I was using 165MB & now I am down around 140MB. Note that I have been around that number throughout the day & that was already down from 350MB earlier when I was forcing this session to use memory.

Another report here, Out-of-control working sets.

@therube:
could you give your treatment to latest development build 1.9.4.6?
It should be much better (at least, it is just perfect on trunk).

NoScript 1.9.3.3, SeaMonkey 2, Intel.

This is an existing sessions from a day or two ago, that had just been sitting.



Mem at 260MB, CPU virtually nil.


NoScript 1.9.4.6, SeaMonkey 2, Intel.

Installed NoScript 1.9.4.6, Session Restore kicked in & reloaded all the existing pages/tabs (10/43). The pages reloaded & (so far) I've done nothing more.



Note that Mem dropped to 150MB. (That is not uncommon when restarting from Session Restore.) & CPU is a big fat ZERO .

Now that's as far as I've gotten ... so far ...

Haven't done a whole lot. Mem is up a bit. Letting it sit a bit, I see the spikes again, about 8%.
Haven't messed enough to tell what will happen once I load memory up.

About to close down.

Have most, but not all windows closed. Mem has dropped from 218MB to 167MB. Still have spikes, 5% (at end of graph).
Given the little I have done so far with this, looks better. Memory looks to be releasing. Spike (so far) seem inconsequential.

Not much of a workout this time. Have not looked at SeaMonkey 1.1.17 at all yet.

NoScript 1.9.4.7, SeaMonkey 1.1.17, AMD.

Opened my "normal" stuff. ~12 windows/55 tabs. Let it sit.
Memory & CPU look good.



Closed most, but not all, Mem dropped from 187MB to 145MB. CPU looks good.

latest development build 1.9.4.8 is probably the best NoScript/ABE release to date, and hopefully the release candidate.
The performance boost is huge, thanks to a rather rocambolesque DNS activity parallelization, and memory footprint is negligible.
Pending showstopper bugs, it will finally go stable before the end of this week

Congrats, installed it now and testing it out.

Giorgio Maone wrote: thanks to a rather rocambolesque DNS activity parallelization,

Ditto what Guardian said, and you'll have to pardon me, my English isn't too good: It's like garlic? .... aaah, smell the DNS!