搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.