NoScript suddenly not working

[AuntyJack]

When I opened Firefox up today I noticed that NS was showing the message "In order to operate on this tab, NoScript needs to reload it. Proceed?" - clicking on "yes" seems to reload the tab, but the message just keeps showing. Some pages, surprisingly act like NS is running normally. I have rebooted Firefox, removed NoScript and installed the latest version, but the idiocy keeps occurring. Searching Google only points to this happening last year, and no fix. Any ideas as to what is going on? The only issue I can think of is I'm still running Firefox 57 and it is saying it's out of date, but I would have expected NoScript to grumble about that in the meantime.

This is really driving me nuts.

[Giorgio Maone]

Which version are you looking at (to tell just hover the NoScript icon or open the NoScript Options page)?

[@ALoss2]

Same exact thing has started to happen to my browsing today...

When I attempted to visit the BABYMETAL LiveNation event page noted below, the NoScript icon showed blocked scripts in the thousands and counting with Task Manager showing Firefox at 52% of a quad-core CPU and 22% of 32GB RAM.
https://concerts1.livenation.com/event/ ... 1519970033

[@ALoss2]

NoScript 10.1.7.2
Firefox 59.0

[xaex]

I am also getting the same reload message on amazon.com. The same message happened with an update several months ago (https://forums.informaction.com/viewtop ... 33&p=93498)
I'm using Firefox 58.0.1 and NoScript 10.1.7.2

[AuntyJack]

Which version are you looking at (to tell just hover the NoScript icon or open the NoScript Options page)?

I'm using 10.1.7.2

[pretty_username]

I have got the same problem on Amazon and Google.

"In order to operate on this tab, NoScript needs to reload it. Proceed?"

If I klick ok, the page reloads but Noscript shows the same message. And again, and again...


Problem startet today with new Noscript version 10.1.7.2. on Windows 7 with Firefox Quantum 59.0 (64 Bit)

[User8741]

Can confirm.

FF 59.0 (64b)
NoScript 10.1.7.2
Example of page showing this 'reload'-message: https://nl.flyingtiger.com/

[barbaz]

I see the reload message on amazon.com, but clicking OK does get NoScript working for me.

[Southern]

Same thing happening here on various sites, including ones that were fine last night and including this one.
Had to disable NoScript to see the confirmation code Captcha on this page in order to enter this post.
Started today.
Firefox 58.0.2 (64 bit) Noscript 10.1.7.2

[CleverUsername]

I'm seeing the same behavior as well. If you go here: http://www.cracked.com/article_25471_5- ... exist.html, I get a noscript icon indicating two sources. If I click the icon, I get the prompt to reload the page. If I click OK, the page reloads. The icon counter briefly goes to 15 before going back down to 2. This page: http://www.cracked.com/blog/4-ways-your ... lly-wrong/, the counter is 16, and if I click the NS icon, it asks to reload. When it does, it stays at 16.

Firefox 59.0 / 64-bit, Windows 7 w/ NoScript 10.1.7.2.

i.crackedcdn.com and ui.crackedcsn.com are both in my trusted list. beacon.cracked.com is untrusted. A bunch of advertising site are marked as untrusted, including google ones.

[Guest]

I checked the babymetal site mentioned above and closed it after a second or so with NS showing 50000 (!) scripts. Then I updated uBO from 1.5.10 to 1.5.14 and all is fine again. Any idea what's going on?

[Guest]

Need to take back my last statement. No relation to uBO. It worked fine for a moment after installation now the thousands of scripts are back. It's NS that's broken.

[Giorgio Maone]

Should be fixed in latest development build,
v 10.1.7.3rc1
=============================================================
x Fixed infinite script count report loops on some sites
(thanks AuntyJack, @ALoss2 and others for reporting)
x Fixed localhost not being recognized as a domain (thanks
skriptimaahinen for patch)
x Fixed regression causing NOSCRIPT element and META refreshes
not to be emulated anymore on script-disabled pages (thanks
barbaz and fatboy for reporting)

[lilmonkey]

It seemed to have been fixed for a while, but now the message is back in an endless loop.

"In order to operate on this tab, NoScript needs to reload it. Proceed?"