ALL pages are blocked until manual reload in Firefox

[theonlyandy]

Hello there.

Since quite a while I have the problem that NoScript forbids every page that I open.
Only after I refresh the page, it will allow things based on the configured rules.

I don't think it's a problem of my configuration, since I couldn't find any option like that.

Is anybody else experiencing the same issue? Is it known maybe?
Thanks for any advise.

I'm on 5.0.3rc2, but I'm having the problem for a while now, it started easily six upgrades ago. Firefox is 52.0 64-bit.

I can reproduce the issue in a blank profile after installing NoScript (which actually installs 5.0.2), and activating
> Temporarily allow current top level site, second level domain.

[therube]

Any other changes to NoScript settings?

Is it only an icon indicator not accurately reflecting status or are scripts actually blocked?
(I see the former regularly.)

[HappyNoScriptUser]

I also experience this issue, but just for some sites,

As an example, it happens with the site https://www.dnb.no/

The scripts will work (be temporarily allowed) if I just click this link..
- however, if I either use my bookmarked version of that page,
or, manually type in ALL of the URL (including the https: prefix and everything),
then its' scripts will not be temporarily allowed,
even though the NoScript option..

Temporarily allow top-level sites by default
* Base 2nd level Domains (noscript.net)

..is turned ON.

The scripts are actually blocked,
as the page is telling me it will not work since JavaScript is turned off.

I noticed that if I just entered "dnb.no" or "www.dnb.no" or even "http://www.dnb.no" in the URL field,
the scripts would be temporarily allowed,
but that was just because there was an automatic reload into the https:// version.

Also, this just happens the first time in a Firefox instance.
If I have several Firefox windows opened,
then closes the dnb page, then it will have its' scripts temporarily allowed
if I try to open a new window and go to the dnb page.
To trigger the issue again, I have to restart Firefox.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Also, I don't know if this is related, but..

When a page is temporarily allowed,
the "Forbid page.com" was in the old days in Italic font.
While the Whitelisted pages had a "Forbid.." in normal font.
But now, it seems that also (most of) the temporarily allowed pages have a "Forbid.." in normal font.
The exception seems to be e.g. that "dnb" page
- after it has been reploaded, it shows "Forbid dnb.no" in Italic font.

I use a.t.m. Firefox 52.0.1 (32-bit) and NoScript 5-0-3rc2,
but just as O.P. wrote, this issue started.. ..a while ago.
Maybe 3 - 6 months..?

[barbaz]

Using NoScript 5.0.3rc2, I don't see these problems in SeaMonkey '2.49pre' (based on Firefox 52.0 release). Nor in Firefox 52.0.1 in a clean profile with only NoScript installed.

Do you guys have e10s enabled?

[HappyNoScriptUser]

Hmm.. I think I maybe have solved the riddle for my own pc, at least.

It seems that Firefox - without any extensions - will start up two processes when it is run.

One is the "parent" process;
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe"

The other will be a "child" process;
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -contentproc --channel="xxxx.0.1234567890\123456789" -greomni "C:\Program Files (x86)\Mozilla Firefox\omni.ja" -appomni "C:\Program Files (x86)\Mozilla Firefox\browser\omni.ja" -appdir "C:\Program Files (x86)\Mozilla Firefox\browser" xxxx "\\.\pipe\gecko-crash-server-pipe.xxxx" tab

(xxxx is the process ID of the parent "firefox.exe" process)

This will also happen when NoScript and / or a lot of other extensions is loaded,
and so, this will not make any of the issues appear.

HOWEVER.

There are some extensions which makes this extra, 2nd firefox.exe child process not appear.
And, when this happens, that issue with some sites (e.g. the "dnb.no" page) not having temporarily scripts allowed..
- and also the issue with the non-Italic "Forbid..." NoScript menu..
- will show up.

So, which are those extensions, then?

At the moment, I have found these 5:

KeePass Helper (version 3.0.2.1-signed.1-signed)
https://addons.mozilla.org/addon/keepass-helper/

HTML5 Notifications (version 1.2.2.1-signed.1-signed)
https://addons.mozilla.org/addon/html-notifications/

Phoenix (version 1.7.5.1-signed.1-signed)
https://addons.mozilla.org/addon/phoenix/

Server Spy (version 0.2.3.1-signed)

URL Flipper (version 3.1.1.20.1-signed.1-signed)

Based on this list,
one may assume that every extension with a
"1-signed.1-signed" or "1-signed" string at the end of their version number
would make that 2nd firefox.exe child process disappear, however, both
Lazarus: Form Recovery (version 2.3.1-signed.1-signed)
and
DOM Inspector (version 2.0.16.1-signed)
will make that 2nd firefox.exe child process appear,
so it's not related to that..

[HappyNoScriptUser]

Regarding the "e10s"..:

YES! It IS related to that..!

To start with the conclusion, it seems that..

..when one of the e10s-non-compatible Firefox add-ons are loaded,
this will block any "firefox.exe" child processes,
and then, those issues with NoScript will show up.


I am sorry I didn't start to look at this earlier!
For some strange reason, I thought that "e10s" was about "localized versions" of Firefox/extensions,
so, when you wrote about "e10s", I just thought
"..that's not relevant to me, since I only use the en-US versions."

But today, I thought, let me - just to be sure - check out what that "e10s" really means..
..and then, I found out it was about multi-process Firefox..!

I had never before seen any more than one, single "firefox.exe" process..
..obviously, since I had several e10s-non-compatible Firefox add-ons loaded.
Only yesterday, when I disabled also the last 2 of those;
the "KeePass Helper", and the "URL Flipper" extensions,
did I notice something strange;
- I got this extra "child" process, which I mentioned.

And now, after reading more about "e10s" on the
http://www.ghacks.net/2016/07/22/multi-process-firefox/
and
http://www.ghacks.net/2016/02/15/change ... efox-uses/
- I now know how to change the preference

Code: Select all

dom.ipc.processCount

into, say, 40, so that each window/tab will run in its' own process.

This is very good news for me, since I often have 20-30 windows,
and once in a while, there is a script (e.g. that "jquery.lazyscript") which will
consume all of the CPU power for, like, 30-120 seconds.
Since there is no response, I can't close the bad window,
the only option was to kill the whole process.
But now, I can instead just kill the one, single bad child process!

[barbaz]

I am sorry I didn't start to look at this earlier!
For some strange reason, I thought that "e10s" was about "localized versions" of Firefox/extensions,
so, when you wrote about "e10s", I just thought
"..that's not relevant to me, since I only use the en-US versions."

You were thinking of l10n (localisation) aka i18n (internationalisation).

Thanks for reporting your findings, but I still can't reproduce the problem in Firefox 52.0.1, clean profile, following these steps -
1) install NoScript latest development build
2) go to about:support, make sure e10s is disabled
3) Bookmarks menu > Show all bookmarks. In that window, bookmark "https://www.dnb.no/"
4) NoScript Options > General, check "Temporarily allow top-level sites by default" and select "Base 2nd-level domains"
5) open a new tab, then Bookmarks menu > New bookmark (the bookmark created in step 3)

[HappyNoScriptUser]

I am sorry I didn't start to look at this earlier!
For some strange reason, I thought that "e10s" was about "localized versions" of Firefox/extensions,
so, when you wrote about "e10s", I just thought
"..that's not relevant to me, since I only use the en-US versions."

You were thinking of l10n (localisation) aka i18n (internationalisation).

That is true, it was the "l10n" I was mixing it up with!

But... this is very strange.

Today, I do not get the issue with dnb.no not having temporarily allowed scripts.

I still get the "issue" (if you could call it that) with the "Forbid page" for all temporarily allowed pages in non-Italic fonts, though..

But, this is not NoScript's fault, it must be those e10s-NON-compatible add-ons' fault.

E.g. when I enable the "URL Flipper" add-on, I get NoScript's "Forbid page" for all temporarily allowed pages in non-Italic fonts
(in addition to the about:support -> "Multiprocess Windows" changing into "disabled by add-ons" )

But, I have not tried this with a clean profile,
it's no big deal, as I, thanks to you learning me about the "e10s"
- just disable all those e10s-NON-compatible add-ons,
and enjoy the comfort of separate processes for each window/tab..!

[ernesto]

cant open facebook, because it's apparently blocked. There's no simple explanation on how to undo this... How's this happened?

[barbaz]

There's no simple explanation on how to undo this...

... except for the simple workaround of clicking the browser's "Reload" button...as said in the opening post of this thread.

[GNUrocks]

Hi all, thanks for thsi topic, as I had the same problem and didn't think of trying to disable addons. Now I did and found out that tabmixplus v. 0.5.0.2 was the addon causing the error. Since I disabled it (didn't miss it as much as I initially thought) only one more time did I have problems and that was curiously the webpage for this addon https://noscript.net/. Don't know why it didn't work, seems to work fine now. Maybe some error on my part. My Firefox version is 53.0b7.

[GNUrocks]

Hi all, thanks for thsi topic, as I had the same problem and didn't think of trying to disable addons. Now I did and found out that tabmixplus v. 0.5.0.2 was the addon causing the error. Since I disabled it (didn't miss it as much as I initially thought) only one more time did I have problems and that was curiously the webpage for this addon https://noscript.net/. Don't know why it didn't work, seems to work fine now. Maybe some error on my part. My Firefox version is 53.0b7.

That was me, got an account now.

[GNUrocks]

Hi all, thanks for thsi topic, as I had the same problem and didn't think of trying to disable addons. Now I did and found out that tabmixplus v. 0.5.0.2 was the addon causing the error. Since I disabled it (didn't miss it as much as I initially thought) only one more time did I have problems and that was curiously the webpage for this addon https://noscript.net/. Don't know why it didn't work, seems to work fine now. Maybe some error on my part. My Firefox version is 53.0b7.

Found 3 others that I need to disable... Don't know why the amount of addons goes up that I need to disable, but anyway I'll try how much frustration it is without them, maybe I'll just reenable them and take the reload every time...

[HappyNoScriptUser]

Found 3 others that I need to disable... Don't know why the amount of addons goes up that I need to disable..

This also happened to me!
One day, the "FlashGot" and "SearchPreview" add-ons were compatible with e10s..
..but then, the next day, I also needed to disable those 2 to get those multiple firefox.exe child processes to spawn.

AFAICS, the only thing that was changed between those two days, was the version of a "hidden"(?) add-on..

"Multi-process staged rollout" "1.6" "true" "e10srollout@mozilla.org"

was changed into

"Multi-process staged rollout" "1.12" "true" "e10srollout@mozilla.org"

And, that "SearchPreview" add-on, it should be compatible with e10s,
so, why is it that I must disable it?
I have a feeling that my profile is way too "dirty",
since I've been using the same one for nearly 5 years.
(E.g. my about:config is full of preferences for add-ons that I stopped using years ago)
So, I'm soon gonna start afresh, with a new profile,
(probably a remove->reinstall of Firefox itself, too).
It's just that, it will take some time to change all the settings of the add-ons after I reinstall them,
so I will have to wait until I feel like I'm up to the task..

EDIT:

Well, what do you know..!

Now, I tried to re-enable the "SearchPreview" add-on again (just to verify it would break the e10s like it did a few days ago).

However, now it is again compatible with e10s (I still see the mutiple firefox.exe child processes)..!
I'd better check for compatible add-ons on that https://www.arewee10syet.com/ page almost each day, it seems..!

[GNUrocks]

All my addons work fine now, without any additional reloads for allowed scripts to work on new firefox beta 54.0b1