Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

Clearing recent history causes very long delay with message "a script has stopped responding"

  • 2 odpovědi
  • 23 má tento problém
  • 3 zobrazení
  • Poslední odpověď od DonDaverse

DonDaverse
DonDaverse
more options

When I take option to "Clear Recent History" from tools dropdown, there is a very long delay EVERY TIME, followed by this message:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: chrome://browser/content/sanitize.js:136

This happens even when Javascript has been disabled. This problem first appeared just after installing Firefox version 4.0

I can proceed to "Clear Recent History" only by again clicking that option after taking option to stop non responding script.

When I take option to "Clear Recent History" from tools dropdown, there is a very long delay EVERY TIME, followed by this message: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: chrome://browser/content/sanitize.js:136 This happens even when Javascript has been disabled. This problem first appeared just after installing Firefox version 4.0 I can proceed to "Clear Recent History" only by again clicking that option after taking option to stop non responding script.

Všechny odpovědi (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Are you clearing the Cookies?

If you do then see if if works better if you do not clear cookies via Clear Recent History.

DonDaverse
DonDaverse Autor dotazu
more options

I have resolved the problem (for now) by uninstalling Firefox 4.0 and reinstalling Firefox 3.6. When 4.1 becomes available I will try 4 again.