InformAction Forums

Hi,

Firefox freezes sometimes on pages with allowed javascript.
Sometimes the warning comes that a script ist not responding. The problematic script is always:
noscriptOverlay.js
line 2276

I disable all other plugins, still the same problem.
With NS disabled it worked fine.

Where can i find that file?

Im running fedora 18, ff 21.0

Well unfortunately with FX yeah presence of NS sometimes causes FX to behave lame. It has a tendency to freeze up or pause (not responding) regularly, specially if you have more than 1 tab running which is the point, so hard not to. Switching between tabs always causes delays and in all fairness although it happens a lot more with NS present, it happens even without it. The only time I have noticed FX running without a problem is when you are running no extensions which again defeats the whole purpose of Mozilla's superiority claim. Fact is that despite Mozilla and FX's insistence that they are highly customizable, extensible and this and that, if you ACTUALLY do that with extensions and so on, anything more than 1 or 2 enhancements and you start getting screwed with performance issues, so their claim is flawed. If they actually put the core functionality people seek through extensions into the genuine code, optimize it, and provide it as-is instead, it would perform much better. This whole concept of adding extensions for every little damn thing you want to do because the browser itself doesn't, is just asinine and ultimately the demise of Fx, regardless of the fact that their "popularity" was based almost wholly on this principle of extensibility. Just my two cents. When it comes to DOM (anything) be it NS checking, parsing and handling all the scripts, be it Adblock Plus checking parsing and handling all the ads and lists, be it Ghostery doing their thing, be it anything that plays with the DOM, during or post render, it will cause a lag and hiccup, period. No matter how well the code is or it is executed due to the platform's failure (the browser). It is not well enough written or optimized for the things it claims and wants to do, screwing everything else and the user experience.

My Problem is not a small lag. Firefox hangs sometimes for a minute or even more. Normall lag, which i noticed also early was at most a few seconds.
And then it is again usable for a long time without any problems ...

This is probably a bug, i can not imagine that it is not possible to make this without this problem.

I hoped somebody could tell me where i find the source files of noscript, so that i could have a look on my own, because i was not able to find the noscriptOverlay.js file ...

alfa_1024 wrote:My Problem is not a small lag. Firefox hangs sometimes for a minute or even more. Normall lag, which i noticed also early was at most a few seconds.
And then it is again usable for a long time without any problems ...

Understood, what I meant and still do is that the delays are consistently present with Fx no matter NS or not. I have a profile with no NS and it happens ALL THE TIME. Do you use Adblock Plus? If so there is well known history of Adblock interfering with NS causing memory leaks and instability due to the way they handle the DOM for removing the "ads" so you might consider that its not NS that's causing it, but rather a combination, try Standard Diagnostics.

This is probably a bug, i can not imagine that it is not possible to make this without this problem.

Honestly, if it was that prevalent we would have heard more about it by now, so chances are its localized to a few like yourself due to other factors. Not saying its not there, but chances are slim its NS.

I hoped somebody could tell me where i find the source files of noscript, so that i could have a look on my own, because i was not able to find the noscriptOverlay.js file ...

All of NS source can be viewed simply by going to the NS extension directory and looking at the files inside the JAR or if you do extracted, then they are already there, no secrets there.

This bug might shed some light (or not) https://bugzilla.mozilla.org/show_bug.cgi?id=639186

If the file (noscriptOverlay.js) and line (2276) are correct, it might happen only on page load/unload for web pages with lots (thousands?) of plugin objects.
Might it be the case?

Sorry for the trubel.

It was unrelated to NoScript - it seems i havent tested without plugins long enough to enconter the problem.
Here is the Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=964693

thanks for the help