I don't know what the script does.

If the script is something Firefox is applying over and over, exiting Firefox should cure that.

If the script is something that is now running on the website, then you need to stop it there.

Websites can create something called a service worker to do things even when their tab is closed. To see whether you have a service worker for the site, type or paste the following into the address bar and press Enter to load it:

about:serviceworkers

If there are sites that should no longer be running scripts in Firefox, you can disconnect them using the Unregister button.

Extremely useful link thank you.

Whilst did not solve the problem because Discord does not seem to be creating a serviceworker command... what you have given me is probably even more useful than solving the problem.

Though so for a more indepth description of the issue. When I sign into Discord on the browser service, the script text can be put into specific open tabs, to run through and delete all known text from a user ID in a specific html code tab. The issue with it, is that i believe it is still running. Everytime I open the page, though I ran the code originally more than a week ago. I believe this, because I still get new "throwback errors" ie, errors that existed whilst i ran the script. Which seem to be reappearing themselves when i enter into the browser Discord now. Ie, the queries are current, though they should not be.

Looking at the blue links on the right [first image], they seem to be workers [second image is the 1/2 pages of the printout]. Though do not show in the worker list [about:serviceworkers]. But I just have a feeling this is affecting other things... this error, showed up in normal processing of the code. It is an inability to connect to an outsourced part of the actual program Discord (ie, originally this is a non-ability for the script to associate to spotify through discord coding, as spotify and discord have a partnership somewhat), whilst rewriting other areas localised to Discord itself. It did not conflict with the script command's function itself (it worked), but this error exhibited itself every now and again.

It is alrite. If the issue isn't something common to you, its okay. I presume a reinstall of firefox to absolve its issue would also work. Signing in and out of the browser program did not work, merely closing it did not work... i am hoping eventually it will solve itself.

Thank you for the data you gave me :hugs:.