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!

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

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

  • 2 réponses
  • 23 ont ce problème
  • 1 vue
  • Dernière réponse par 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.

Toutes les réponses (2)

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.

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.