Performance and Website Connection Issues

[GµårÐïåñ]

I have been experiencing an issue that I believe might be related to this but if not I apologize and we can split it into another topic. I have been getting alot of sudden connection drop to the website (net:error page) after allowing a site and no matter how many times I hit refresh nothing happens. If I close and restart Fx it seems to work fine. This happens ALOT and not just on specific sites which makes it hard to give urls for testing, seems not to be site specific but rather NS specific. In a profile without NS, not a single drop or net:error happens.

Additionally I have noticed that since I installed the latest .96 build, there is a pause/lag in all activity that occurs in Fx no matter what you are doing, no matter what website you are on and it comes in waves of 60 seconds at a time and is consistent and very eerie. I using the exact same setup in another profile that has the same extensions, MINUS NS (designed for testing things like this) it works perfectly, no hiccup, no glitch, nothing, any ideas?

[therube]

After installing 1.9.7, & restarting, Session Restore loading my open pages, a number of them, came up (similar) to:



That was unexpected. Don't recall having seen that before.
(It could be, perhaps related to, that I had been logged in under a different User, & my main (XP) User session had spooled out... Come to think of it, I had manually deleted /Cache/ folders, so perhaps that's why Session Restore had trouble with certain pages? Not sure how Session Restore works as far as reloading from cache vs. reloading fresh?)

Otherwise I don't know that I've noticed anything too abnormal.
Some pages may be slow for the progress bar to finish, but I don't know if that is NoScript related or not? (This site is always slow for the progress bar to finish.)
One time after I Allowed a page (I think it was Yahoo mail?), the page went blank. I thought that was the end of it, just no page, but eventually & surprisingly the page did load.
There is one forum I go to, when I Post a reply, usually (but not always), it takes a long time before things "register". If during this period, I hit Stop, then (again) Submit, it usually responds straight away.

When you have your issues, Error Console show anything of note?

[GµårÐïåñ]

I caught this reply by accident, I didn't get a notification from the site that you replied to it, that's odd. Anyway, I have not checked for errors, I will check next time but mostly now its just this approximately every 60 second hiccup that hangs the whole thing for approximately 10 seconds and then lets it go, its getting ridiculous.

[Giorgio Maone]

@therube:
yes, most likely session restore was just missing the cache files needed to restore those pages.

@GµårÐïåñ:
Something so dramatic, if caused by the NoScript update alone, would have caused my support mailbox to explode.
Did you check if the problem persists with NoScript disabled and/or with NoScript as the only extension installed?
Have you got any non-standard ABE rule?

[GµårÐïåñ]

Well I suspect once again it must be my imagination if the whole world hasn't written you about it, maybe they don't use their browser so extensively and pause sufficiently that they don't notice as much, I can only speak for myself. The fact is that as I stated earlier in another profile with the exact same extensions, MINUS NoScript it runs fine without any hiccup or any problems, so that's why I am nearly 100% certain its NoScript or some combination of NoScript and another extension. The fact is that .6 release was hugely problematic for many, so its not so unrealistic to believe that its causing more issues, reported or otherwise. If we prefer to just assume its my problem, then I will drop the discussion and wait until your mailbox explodes and we can take it from there.

[Grumpy Old Lady]

Time for you to do the work then? :-)
http://kb.mozillazine.org/Standard_diag ... ion_issues

[GµårÐïåñ]

Thank you, I am fully aware of what to do and have done the work. I don't make it a point of wasting my time posting without having a reason to do so.

[Grumpy Old Lady]

Thank you, I am fully aware of what to do and have done the work. I don't make it a point of wasting my time posting without having a reason to do so.

Just working with you here :-)
I don't seem to be able to see where you tested a clean profile minus NS, then a clean profile plus NS :-)
Or even your full setup minus ABE?

[GµårÐïåñ]

I know and I appreciate that but just because I don't fill up the page with meaningless step by steps of everything I have done, doesn't mean I have not done it. The most relevant observation was the fact that identical set of extensions in two separate profiles with the difference of NoScript reproduced the issue.

Meaning, no need to go down and do everything step normally needed to debug because that is the most significant scenario because it most closely replicates the actual differences down to a single event. And yes, disabling just ABE portion on the profile with the NS didn't change anything, that was actually my first act since its the most unstable feature at the moment.

Plus it isn't sufficient for NS to work by its lonesome in a profile, it needs to behave with other extensions or it makes the use of Firefox for its extensibility a defeated point. Now I suppose there might be an extension that isn't playing nice and if I go through all the 24 extensions currently installed I might find something but the fact remains these extensions have been running side by side with NS for a VERY LONG time, so for them to suddenly start being an issue, I would say it points more towards NS and recent changes since the others haven't been updated in a long while.

There is more to debugging than aimlessly following a list of step by steps, sometime actual observation and keen sense of what is what is far more helpful. Every time we have a chest pain, the doctor doesn't order a full body scan do they? Now I know that most of what I report seems to get the dismissive response but the fact is that much of what I have reported in the past and been ignored ends up being a problem that gets fixed later and no one seems to remember that I reported it. That's why I said maybe if I wait and have someone else report it, it might get some attention.

[Grumpy Old Lady]

I didn't see the logic in leaving NS (Giorgio) hanging out to dry without at least giving him a clue about which extension conflict or which part of ABE might be contributing to your difficulties.
But, as you've asserted that your troubleshooting methods are a matter for you, I'll refrain from contributing further :-)

[therube]

the fact remains these extensions have been running side by side with NS for a VERY LONG time

Then if you revert to earlier NoScript versions, do the problems subside?


At one point, one of my errors tended to point to my DSL connection/modem which tends to flake out every once in a while.