Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox crashes

  • 1 baphendule
  • 1 inale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu philipp

more options

I'm getting a lot of crashes using Firefox 50.1.0 (latest version as of this post) on my MacBook Pro. It's been happening every since I got it about a month ago. It seems to happen after the machine has been asleep for a while. I cannot reproduce it at will by putting the machine to sleep then immediately waking it up. It's possible it would work and it's just intermittent. Anyway, it happens several times a day, even when I'm running in safe mode.

Crash report number: bp-0458f9b9-0130-492a-8c56-fafce2170121 https://crash-stats.mozilla.com/report/index/0458f9b9-0130-492a-8c56-fafce2170121

My MacBook Pro info: 15-inch, Late 2016 2.6 GHz Intel Core i7 16 GB 2133 MHz LPDDR3 Radeon Pro 450 2048 MB Intel HD Graphics 530 1536 MB

I'm getting a lot of crashes using Firefox 50.1.0 (latest version as of this post) on my MacBook Pro. It's been happening every since I got it about a month ago. It seems to happen after the machine has been asleep for a while. I cannot reproduce it at will by putting the machine to sleep then immediately waking it up. It's possible it would work and it's just intermittent. Anyway, it happens several times a day, even when I'm running in safe mode. Crash report number: bp-0458f9b9-0130-492a-8c56-fafce2170121 https://crash-stats.mozilla.com/report/index/0458f9b9-0130-492a-8c56-fafce2170121 My MacBook Pro info: 15-inch, Late 2016 2.6 GHz Intel Core i7 16 GB 2133 MHz LPDDR3 Radeon Pro 450 2048 MB Intel HD Graphics 530 1536 MB

All Replies (1)

more options

hi dland, we are aware of this issue on newer macbooks when they wake up from sleep mode. we are waiting for the release of os x 10.12.3, which should contain a fix for this. you can also follow along at bug 1320048 where we track this issue...