Mozilla 도움말 검색

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

자세히 살펴보기

Firefox crashes

  • 1 답장
  • 1 이 문제를 만남
  • 5 보기
  • 최종 답변자: philipp

more options

I use Macbook Pro 15 with Sierra 10.12 and Firefox 50.1. Since installing Firefox (two weeks ago), every time I open the Macbook's lid and wake up the system, I see the Firefox crash reporter. I checked my Firefox, add-ons and OS to see if they are updated, I disabled unnecessary add-ons, I restarted the Firefox in safe-mode; none of them solved the problem. The only help that they did was by doing so, the Firefox crashed not at every system wake-up, but by a random time (sometimes after one hour sleeps, sometimes 6 hours). Firefox hasn't had crashes during the time I used the system, it crashes just at the system wake-ups (and I noticed in console that it is not due to the system wake-up itself, but due to some errors after couple of hours) Any help would be appreciated. My crash-id is bp-2024233a-bafe-485c-9ba0-a68fe2170108

I use Macbook Pro 15 with Sierra 10.12 and Firefox 50.1. Since installing Firefox (two weeks ago), every time I open the Macbook's lid and wake up the system, I see the Firefox crash reporter. I checked my Firefox, add-ons and OS to see if they are updated, I disabled unnecessary add-ons, I restarted the Firefox in safe-mode; none of them solved the problem. The only help that they did was by doing so, the Firefox crashed not at every system wake-up, but by a random time (sometimes after one hour sleeps, sometimes 6 hours). Firefox hasn't had crashes during the time I used the system, it crashes just at the system wake-ups (and I noticed in console that it is not due to the system wake-up itself, but due to some errors after couple of hours) Any help would be appreciated. My crash-id is bp-2024233a-bafe-485c-9ba0-a68fe2170108

모든 댓글 (1)

more options

hi, this is a bug in mac os x leading to a crash of firefox when the machine wakes from sleep. we are waiting for the general release of osx 10.12.3 to get this fixed. you may also follow along in bug 1320048 where we are tracking the issue.