Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

Frequent Unresponsive script error chrome://global/content/bindings/text.xml:32 w/ Firefox frozen

more options

I FREQUENTLY get a

Unresponsive Script: A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: chrome://global/content/bindings/text.xml:32

after Firefox became frozen for about 20+ minutes. I tried disabling addons and Firefox safe mode, STILL get this error quite a bit

I FREQUENTLY get a Unresponsive Script: A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: chrome://global/content/bindings/text.xml:32 after Firefox became frozen for about 20+ minutes. I tried disabling addons and Firefox safe mode, STILL get this error quite a bit

تمام جوابات (1)

more options

Do you see any connection between pages that generate this error and the use of the Flash plugin? Incompatibility with the Protected Mode feature of the Flash plugin is one possible cause for slow script errors (on pages that use Flash).

The Protected Mode feature has security benefits, but seems to have compatibility issues on some systems. You can disable it by creating or editing a settings file. The following pages/posts provide different approaches for that:

Flash needs to completely unload from memory (exiting and starting Firefox up again might help) before this takes effect.