Avatar for Username

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Μάθετε περισσότερα

Αυτό το νήμα αρχειοθετήθηκε. Παρακαλούμε κάντε νέα ερώτηση αν χρειάζεστε βοήθεια.

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

  • 2 απαντήσεις
  • 23 έχουν αυτό το πρόβλημα
  • 3 προβολές
  • Τελευταία απάντηση από 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.

Όλες οι απαντήσεις (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 Ιδιοκτήτης ερώτησης
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.