Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

How to stop firefox Unresponsive script messages: Script: chrome://browser/content/tabbrowser.xml:0; Script: resource:///components/nsPrompter.js:68;

  • 7 odpowiedzi
  • 587 osób ma ten problem
  • 7 wyświetleń
  • Ostatnia odpowiedź od philipp

more options

When I let the browser run for an extended period of time, perhaps 3= hours I get a messages like: Unresponsive script messages: Script: chrome://browser/content/tabbrowser.xml:0; Script: resource:///components/nsPrompter.js:68;

When I let the browser run for an extended period of time, perhaps 3= hours I get a messages like: Unresponsive script messages: Script: chrome://browser/content/tabbrowser.xml:0; Script: resource:///components/nsPrompter.js:68;

Wszystkie odpowiedzi (7)

more options

Has anyone come up with a decent solution to this yet? It's getting really annoying with this error message coming up every time I clear my cache or try to exit firefox.

The only answer I've found so far is deleting cookies manually every time - this is a pain, there must be a more permanent solution. Please help Mozilla.

more options

I've been getting this too on my Toshiba E205, for a really long time. It seemed to come on suddenly, but I can't trace it to one event. It seems possibly unique to Windows 7 because I get similar errors on an HP 6560 I just got last month, and it only runs IE.

For me, it happens when I resume from Hibernate or Sleep and I have Firefox running (or IE on my 6560). IE on my Toshiba doesn't seem to be subject to it.

Interesting that nicolamarie traces it to cookies. I have my cookies set to ask me every time. I wish web sites would have a list of required cookies so users can remove those from the block list.

more options

To add to the confusion, the problem has come up only after (auto-)upgrading to Firefox 9.0 here. Previous FF versions didn't show this issue.

I'm on Suse 12.1, Linux kernel 3.1.0, KDE 4.7.2, in case this matters (which I don't think it does).

more options

I don't know who create this script I know this bad script breaks through brouser Mozilla and site google I use Fedora Electronic Lab

is alert Script: chrome://global/content/bindings/popup.xml:20

Script: https://mail.google.com/mail/?ui=2&view=js&name=main,tlist&ver=CGe7GQTFIGk.en.&am=!ogkKXeTuuxbZAt2LwXy2hE4qgECz60SNLGlyWb6LDzXMkwmVenMnW75mNSwqoG5jbA:395

Zmodyfikowany przez krikoon w dniu

more options

I have the same problem, however I do NOT have Chrome, and I'm running xp, and the unresponsive scripts happen with almost every page I try to load. It has recently started happening after I sign into gmail. SO irritating! Please come up with a fix SOON!

more options

i get a series of unresponsive script errors in a row from the gmail page when i have the firefox browser open for extended periods. to make it worse, it slows down my entire system, so everything freezes, skype conversations close, etc. really, really, really annoying. annoying enough to consider going to chrome. totally don't want to though. i hate the all eggs in one basket thing (google, google, google). please help.

more options

hello courtneyj76, i think it would be better to open a separate question where you can provide more detailed information about your system (copy it from help > troubleshooting information).

please also observe how much resources (cpu & memory) the firefox.exe process and plugin-container.exe are consuming in the windows task manager (you can bring it up by pressing ctrl+shift+esc) when the freezes occur & add it to the problem's description. this will make it easier to diagnose the issue. thank you!