Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Firefox 35.0 uses 100% cpu on Mac Yosemite 10.10.1 then either crashes or needs force quit.

  • 4 отговора
  • 24 имат този проблем
  • 13 изгледи
  • Последен отговор от jaf1948

more options

I have had this problem since installing Yosemite and using 34.0.5. I upgraded yesterday to 35.0 but still the same problem. Firefox will work happily for a while and then suddenly will use 100% cpu. I have disabled all extensions and plug-ins and that makes no difference. If I use Java (8-25), it will usually make it crash but not always.

To make matters worse, the crash report appears in Greek (which is being discussed in another question already).

I have had this problem since installing Yosemite and using 34.0.5. I upgraded yesterday to 35.0 but still the same problem. Firefox will work happily for a while and then suddenly will use 100% cpu. I have disabled all extensions and plug-ins and that makes no difference. If I use Java (8-25), it will usually make it crash but not always. To make matters worse, the crash report appears in Greek (which is being discussed in another question already).

Избрано решение

Всички отговори (4)

more options

Избрано решение

Have you tried resetting Firefox? Refresh Firefox - reset add-ons and settings

more options

Yes, I tried resetting and when that didn't work, I used the Mac App appcleaner to delete everything about Firefox (the program itself and all connected files but took a copy of the profile first) and did a complete reinstall. Still the same.

more options

Fascinating. When I was on FF 34.0.5, I did the reset as explained above and the problems were still there. I did a reset again today using 35.0, and so far the problems have not come back. I will leave it 48 hours and if there is no recurrence, I will asuume the problem is cured.

To anyone else, therefore, make sure you are on 35.0 before doing a reset (refresh).