搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox crashes

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 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.