We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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).

more options

Problem solved !