t-mobile.com hangs Firefox

[ElvisDumbledore]

I have tried running on a fresh profile with only https everywhere and noscript running. Upon loading the site I need to "temporrarily allow all" twice. After the second round I get an error from Firefox Quantum 61.0.2 (64-bit) that a script in the extention noscript is causing a slowdown do I want to disable it for this website. Just getting started diagnosing will keep updating as I find out more.

The offending script is coming from forsee.com.

[therube]

Confirmed.
Just don't ask me how I managed to do it?

Extension/Script warning
Modal dialog
High CPU usage
10.1.9.1rc1





Something like...

URL: https://www.t-mobile.com/

allow t-mobile.com
allow all this page
scroll through the page
see the link for the "cheaper" plan
open that in a new tab
allow globally on that tab

And it was around that point that the script warning message message came up, along with high CPU.
At that point, NoScript icon was not behaving properly & Modal may have occurred simply by clicking elsewhere?
And stopping the "script", high CPU usage was not easy to accomplish.
Not quite sure just what steps accomplished that?
I was thinking of just quitting the browser & restarting, but farting around eventually did get things to subside. But then I ended up duplicating the same shortly thereafter.
I'll also note the script warning also showed up on some (not all) open windows.

[skriptimaahinen]

ugly hack: since now we use registerContentScript instead of the
filterRequest dynamic script injection hack, we use top.name
to store per-tab information. We don't want web content to
mess with it, though, so we wrap it around auto-hiding accessors

I think you might be leaking somewhere, as I found this in the top.name:

https://pastebin.com/raw/mvJp0Grs

Needles to say your little regexp didn't survive it.

Somewhat related is that hitting Back will apparently retain the top.name, thus you can load the t-mobile.com page, hit back button to go to completely unrelated page, refresh that page and still trigger the bug.

Also likely related:

1. open "regular" page
2. navigate to some RSS feed page (e.g. https://noscript.net/feed)
3. hit back button
4. observe the permission line from the RSS feed page in the popup

[Giorgio Maone]

Please check latest development build,
v 10.1.9.2rc4
=============================================================
x More efficient window.name-based tab-scoped permissions
persistence
x Fixed URL parsing bugs