InformAction Forums

I'm having the same issue for months now. Using Windows 7.
Yesterday I also tried to enable NoScript again after I disabled it a week before to revalidate that it's the cause. My browser Immedeadly got stuck and even the button to disable NoScript again took a whil till it reacted.
Please try to fix this bug as soon as possible. This topic is open since Janurary and it makes NoScript quite less useful.

Appears to be correlated with large numbers of windows and tabs being opened

Depending on what "large" is, I'd say not.
SeaMonkey, I can (& have always) had umpteen millions of windows/tabs open. (Umpteen, that tells you a lot .)
(Umpteen, looks to be only 18 windows, 357 tabs.)

FF, only three 3 & 18 tabs - so that is nothing (compared to large, much less umpteen).

Figures, eh, an hour and 27 minutes ago (11:02:53 AM 11/11/2022).

I'*ve recorded a Log from the Debugging-Console in Firefox.
Started when I started NoScript, ended when the issue occured and firefox stalled:
https://destra.uber.space/files/console ... 4-39-3.txt
(I've removed some private information)

The log looks quite harmless.

@Destranix

What OS (& FF version)?

About how long did it take until things failed on your end?
(With me, typically I was running for about 1 week, without closing, before failing. And then the odd times, I could be dead within an hour.)

Today I started the browser and it was already having this issue. That is a speed record. oO
Disabling NoScript cleared that up, as usual. But also has reached a point where the addon is basically unusable.

therube wrote: ↑Thu Nov 17, 2022 5:20 pm @Destranix

What OS (& FF version)?

About how long did it take until things failed on your end?
(With me, typically I was running for about 1 week, without closing, before failing. And then the odd times, I could be dead within an hour.)

Windows 7. Firefox 107 (if no update occured till yesterday).
Took about a few hours (but that is not relevant, it's obviously some kind of race condition occuring more propable after long time but that can occur also after short time).

Hi all,

Just wanted to add that I now also seem to have this problem. Started a couple of days ago. Firefox suddenly stops loading pages and it seems to be tied to NoScript somehow. I'm on Windows 7 with FF 102.5.0esr.

Also, Firefox has spawned A LOT of processes. I have not checked the task manager in a long time, so I don't know if this is normal these days. Is one-process-per-tab a thing now?

Any updates on this issue? I'll try to investigate some more in the coming days myself.

Cheers
A.

I think I've managed to see (but not to reproduce) this issue a couple of time now, and I've observed that when it happens the background process of any extension is simply gone. This affects all the extensions, but some in more visible ways than others. For instance, if both NoScript and uBlock have their popup menu completely empty and unoperable. Even built-in extensions, like the screenshots button, stop working.

This is particularly evident for NoScript users because NoScript, for security reasons, falls back to blocking as much as possible when something gets broken (in this case, cannot retrieve its global settings because the background process is gone), but I'm gonna open a bug in Mozilla's tracker because this actually breaks all the WebExtensions.

Latest development build 11.4.14rc1 implements a work-around, trying to restart NoScript as soon as you click its toolbar icon if the background process cannot be reached.

Giorgio Maone wrote: ↑Sun Dec 04, 2022 9:58 am but I'm gonna open a bug in Mozilla's tracker because

Greate that you maybe found the issue. Can you linke the bug-report here as soon as it's created?

therube, I'm wondering if the behavior you've been dealing with and my post about url shortcuts are somehow related. My issue is with Content Security Policy, and a couple posts back in this thread you had Content Security Policy blocking things.
Perhaps there is a conflict going on between Firefox and NoScript on managing this policy.

Sorry, I thought I was on the last page and no solutions had been discovered, and did not see that Mr. Maone found a possible workaround for the issue.

Fix 11.4.14rc1 helped with my problem, no loading sites 19 cards on newest firefox

Since I (now) frequently restart FF (daily, in most cases), I held on to the older NoScript, 11.4.13rc4 - specifically disabled updates, & guess what?
Today, with the browser opened earlier this morning, just now, "Firefox stops loading pages until NoScript disabled or Firefox restarted" .

So, the old version is still broken, in current Nightly, 20221226035608.


Now, I can throw in the current NoScript RC, 11.4.14rc1 & see how that goes .



I will note, that simply installing 11.4.14rc1 was not sufficient to get things working.
As in, NoScript initially disabled, so I could "network", update NoScript to 14rc1, & re-enable NoScript - at that point, still I could not load pages.
(So had to disable again to update this post.)

And an actually browser restart (I take it ?) will be required before 14rc1 actually becomes functional.
Yes (that was the case).

Another user facing the same issue as above!

I noticed that when the loading error occurs, all extensions have been terminated -- the FirefoxCP WebExtensions process no longer appears in Activity Monitor.