InformAction Forums

First I would like to thank you for your great add-on!
Here is my report:
Installed Versions:
• Firefox version 65.0 (also relevant to previous versions: 64, 63)
• NoScript version 10.2.2rc2 (also relevant for latest stable versions: )
• Updated Windows 7 SP1

Description:
Upon loading the following page (PLEASE DO NOT LOAD IT YET):
https://www.datascience.com/blog/stock-price-time-series-arima
Firefox process starts consuming A LOT of memory: about 10 GB increase in few seconds,
and still increasing consuming virtual memory swap file.
The computer becomes sluggish, and there is a need to kill Firefox process.

Work around:
Either load the above mentioned page in another browser or
disable NoScript add-on BEFORE loading this page in Firefox.

Thanks and all the best

Cool.
Never seen so much memory eaten (14 GB) so quickly.

But I don't see where it is a NoScript issue, as I see the same in a brand new Profile - no extensions.
(I did get a "script is slowing down FF" message, which I told FF to stop it.)
(FF 65 tested above, new Profile.)



SeaMonkey 2.49 x64 crashes "instantly" (essentially as soon as I type in the URL).
(I see a quick [process manager] blip ~3.5 GB RAM, then it disappears.)

SeaMonkey 2.53 x64 (akin to FF 56) got up to 17 GB before a "stop script" warning came up.
Clicking, Stop, & memory has reduced to 12 GB & except for the "little" fact, all looks well .

An ancient version of Chrome (38.x), 350 MB.



Whatever this means:

X-UA-Compatible: IE=edge,chrome=1

Adding NoScript into the mix, either NoScript 5 or 10...


SeaMonkey 2.53, 250 MB.
SeaMonkey 2.49, 281 MB.
FF 65, 800 MB (but then it settled down to ~500 MB).
(I imagine FF was doing all its spyware crap initially.)


So NoScript is actually blocking the errant script.

There are plenty of domains linked to that page.
Seems to be only 1 that is the "bad actor".

Appears to be raviolli77.github.io.
(Well, there are plenty of bad actors on that page , but only that 1 causes huge ram numbers.)

Since you asked: (Wonder how datascience uses that code?)


I'll note that once RAM goes up, the NoScript "dropdown" opens in a non-modal window.



The other "actors":
PS: What would happen if a site used § in its URL?

Here is a clarification:
Loading the page mentioned in FF when NS is disabled DOES NOT cause any problem.
Once enabling NS and then refreshing the page, the memory consumption very rapidly rises.
I clickly closes the tab to avoid long computer slowdown, and the memory is released.
So it seems NS does have some issue here.

If you allow "all", that will happen.
If you run without NoScript installed at all, that will happen.

You can allow all EXCEPT for raviolli77.github.io & you should be OK.

I get the same results on another PC.
Not just reproducing this on my PC:

Loading the page mentioned in FF 65.0 when NS add-on is completely disabled DOES NOT cause any problem.
I disable NS on "about:addons" configuration page
Once enabling NS on "about:addons", and then refreshing the page,
the memory consumption very rapidly rises.
Again,it seems NS does have some issue here.

In my Firefox configuration the memory consumption does not rise up with NoScript disabled. However, it rises tremendously fast with NoScript enabled and all restrictions disabled. And it rises up tremendously fast with a fresh profile without NoScript.

I am using Firefox 65 with NoScript 1.2.2rc2.