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

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

Learn More

Firefox consistently monopolises 99% CPU -- even after fixes suggested on Support pages (deactivate add-ons, run in Safemode, reinstall) (XP, 2GB)

  • 21 απαντήσεις
  • 9 έχουν αυτό το πρόβλημα
  • 3 προβολές
  • Τελευταία απάντηση από rutherford2017

more options

Firefox consistently monopolises 99% of memory -- except, inexplicably, whenever I am on a Mozilla Support page. (I usually have three or four tabs open: hotmail, work email, Linkedin and theguardian newspaper. When I am 'on' any of these pages, Firefox usage is 94-99%; if I open a Mozill Support page, when I am 'on' this page, usage drops below 10%.)

I have tried all of the solutions suggested on the Support site (disabled all add-ons, run in Safe mode, re-installed latest version) but all to no avail. When left unattended for an hour or more, Firefox crashes, but is then "unable" to send a report. I use Windows XP.

Firefox consistently monopolises 99% of memory -- except, inexplicably, whenever I am on a Mozilla Support page. (I usually have three or four tabs open: hotmail, work email, Linkedin and theguardian newspaper. When I am 'on' any of these pages, Firefox usage is 94-99%; if I open a Mozill Support page, when I am 'on' this page, usage drops below 10%.) I have tried all of the solutions suggested on the Support site (disabled all add-ons, run in Safe mode, re-installed latest version) but all to no avail. When left unattended for an hour or more, Firefox crashes, but is then "unable" to send a report. I use Windows XP.

Τροποποιήθηκε στις από το χρήστη Wayne Mery

Όλες οι απαντήσεις (1)

more options

It crashes occasionally, but the most persistent problem is that, by monopolising 97-99% of the CPU, it makes the computer run REALLY slowly.

(Please be kind enough to remind me how to access crash IDs.)

  1. 1
  2. 2