Seemingly infinite loop when using ad/script blockers #8
Description
I am running Chrome "108.0.5359.124 (Official Build) built on Debian bookworm/sid, running on Debian bookworm/sid (64-bit)" according to the about info, with noScript, UBO, and uMatrix extensions (the internet is a toxic cesspool of code, ergo my machines default answer to a sites expectation to run anything beyond stylizing and displaying text is a solid 'You're joking, right?'). When noScript is set to default the script (correctly) does not run and does not produce output, but when set to "temp. trusted" (it, again correctly runs, and) the output detects a few 192.168x.x devices (seemingly correctly though not as many as I know are on the network, but more worryingly), however it appears to get stuck in a loop of checking 10.0.0.0-255 IPs continuously outputting calls to that IP block in sequence. Its possible I have something on the network acting naughty and responding, but nothing Im currently aware of. This machine runs an AMD fx-8350, when the script is running it loads up to about 30%~45% CPU according to the task manager toolbar, and rapidly warms the chip (in fairness I do need to clean out the case, badly. So thermal management is a bit borked, still its quite a raise for just ~40% load in less than a minute).
I am not hip on chrome/website debugging, just thought Id give a heads up in case anyone wanted to look into it.