Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Firefox came up with the unresponsive script message and now if frozen?

  • 4 respostas
  • 18 têm este problema
  • 4 visualizações
  • Última resposta por cor-el

more options

Firefox came up with the unresponsive script message. I clicked 'stop script' but now Firefox has frozen and is not responding to anything I do. I cannot click on anything. It will not let me close it down, uninstall it or shut down my computer.

Firefox came up with the unresponsive script message. I clicked 'stop script' but now Firefox has frozen and is not responding to anything I do. I cannot click on anything. It will not let me close it down, uninstall it or shut down my computer.

Todas as respostas (4)

more options

Can you try to start Firefox in Safe Mode to see if Firefox works properly with no error? You can start Firefox in Safe Mode below:

  • Windows/Mac: Go to Help > Restart with add-ons disabled
  • Linux: Run firefox -safe-mode in the Terminal/Konsole

If Firefox opens up fine with no problems, it's probably one of your extensions that's causing the issue. You can re-enable your add-ons one by one until you find the one that causes the issue upon being re-enabled.

more options

Can't you close Firefox via the Activity Monitor?

more options

Upgraded to FF 33 and installed English dictionary. Now FF is hanging frequently in www.morningstar.com and I believe elsewhere with the following:

Warning: Unresponsive Script

Script: chrome://browser/content/browser.js.17006

I do NOT understand the "chrome" reference.

This is quite annoying. I upgraded to FF 33 in order to try to get back spell checking in Morningstar posts which I lost back at FF 24, as I recall, but it did NOT solve the problem. Now I have this mess.

more options

Firefox uses the "chrome://" protocol to access its own internal files and also access files from extensions, so that has nothing to do with Google Chrome.

You can open such a chrome: link via the location/address bar to inspect such a file and possibly use "Web Developer > Page Source" to jump to a specific line number in the source.