How can one disable the message windows: "Warning: Unresponsive add-on script"?
Hi,
(Firefox 60.8.0esr, up-to-date Debian testing Linux):
I again and again get the following message in a pop-up window (not in the browser, not as a hint on top of the page, but as window):
Warning: Unresponsive add-on script A script from the extension "...." is running on this page, and making Firefox unresponsive. It may be busy, or it may have stopped responding permanently. You can stop the script now, or you can continue to see if it will complete. Script: moz-extension://... [ ] Prevent the extension script from running on this page until it next reloads [Stop script] [Continue]
This happens with different scripts, on different webpages.
And while displaying this window, Firefox actually stops loading and processing anything until I click "Continue", "Stop script" or the close-button of the window. Firefox does not try to continue to work in the background or so. No, it actually causes the real unresponsiveness. Only if I click the message window away, it continues. And it never did not continue yet then.
I know that I have a rather slow computer, but I do not want Firefox to annoyingly remind me of that. Browsing would be fine for me without this message.
I of course searched about:config, and also this forum, but did not figure out how to disable this annoyance for example by increasing a timeout or changing some other value... I tried altering many preferences like dom.max_script_run_time , dom.max_ext_content_script_run_time or dom.max_chrome_script_run_time , but that did not resolve it. Googling for "Unresponsive add-on script" I only found others having this problem (without working solutions) and references to the sourcecode. I will not disable the add-ons. I do not need a fix for an allegedly unresponsive add-on script, because everything in this regard works just fine; i just need an option like: "Always continue, and never ever dare to ask me anything like that again".
So, how can one disable this message permanently?
Thanks in advance!
All Replies (1)
This looks like a problem with an extension as you can see by the moz-extension: link in the screenshot. You can find all GUIDs listed on the about:debugging page.