This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Firefox 48.0.2 just recently crashing with OS X 10.7.5 - Crash Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

  • 2 ŋuɖoɖowo
  • 1 masɔmasɔ sia le esi
  • 3 views
  • Nuɖoɖo mlɔetɔ noremacniai

noremacniai
noremacniai
more options

Signature XUL@0x3177514 | XUL@0x33137cf | XUL@0x3177242 | XUL@0x317d1ec | libsystem_c.dylib@0x3e2b4 More Reports Search UUID a02298b7-39b0-4782-b2e3-ab3b70181121 Date Processed 2018-11-21 12:27:10 Uptime 4,068 seconds (1 hour, 7 minutes and 48 seconds) Install Age 40,039 seconds since version was first installed (11 hours, 7 minutes and 19 seconds) Install Time 2018-11-21 01:05:44 Product Firefox Release Channel release Version 48.0.2 Build ID 20160823121617 OS OS X 10.7 OS Version 10.7.5 11G63 Build Architecture amd64 Build Architecture Info family 6 model 15 stepping 6 | 2 Adapter Vendor ID Advanced Micro Devices, Inc. [AMD/ATI] (0x1002) Adapter Device ID RV530/M56-P [Mobility Radeon X1600] (0x71c5) Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash Address 0x0 EMCheckCompatibility True App Notes AdapterVendorID: 0x1002, AdapterDeviceID: 0x71c5FP(D000-L10000-W00000000-T0100) GL Context? GL Context+ Processor Notes processor_ip-172-31-31-176_us-west-2_compute_internal_9; Processor2015; earlier processing: 2018-11-21T12:28:16.166104+00:00; non-integer value of "SecondsSinceLastCrash"; processor_ip-172-31-31-176_us-west-2_compute_internal_9; Processor2015; non-integer value of "SecondsSinceLastCrash"

Signature XUL@0x3177514 | XUL@0x33137cf | XUL@0x3177242 | XUL@0x317d1ec | libsystem_c.dylib@0x3e2b4 More Reports Search UUID a02298b7-39b0-4782-b2e3-ab3b70181121 Date Processed 2018-11-21 12:27:10 Uptime 4,068 seconds (1 hour, 7 minutes and 48 seconds) Install Age 40,039 seconds since version was first installed (11 hours, 7 minutes and 19 seconds) Install Time 2018-11-21 01:05:44 Product Firefox Release Channel release Version 48.0.2 Build ID 20160823121617 OS OS X 10.7 OS Version 10.7.5 11G63 Build Architecture amd64 Build Architecture Info family 6 model 15 stepping 6 | 2 Adapter Vendor ID Advanced Micro Devices, Inc. [AMD/ATI] (0x1002) Adapter Device ID RV530/M56-P [Mobility Radeon X1600] (0x71c5) Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash Address 0x0 EMCheckCompatibility True App Notes AdapterVendorID: 0x1002, AdapterDeviceID: 0x71c5FP(D000-L10000-W00000000-T0100) GL Context? GL Context+ Processor Notes processor_ip-172-31-31-176_us-west-2_compute_internal_9; Processor2015; earlier processing: 2018-11-21T12:28:16.166104+00:00; non-integer value of "SecondsSinceLastCrash"; processor_ip-172-31-31-176_us-west-2_compute_internal_9; Processor2015; non-integer value of "SecondsSinceLastCrash"

All Replies (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hi noremacniai, as you can imagine, this is not because of a recent update on Firefox's side, and probably it's not something Apple issued either, although you would know better than I. So it could be an add-on or website is triggering the crash, or some other software added to or updated on your system.

If you are getting the Mozilla Crash Reporter form, your Firefox may have logged some data that would help track down the cause of the problem. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox crashes - asking for support" for steps to get those crash report IDs from the about:crashes page, and then post some of the recent ones here.

(You might have copy/pasted from one of those, but the online interface is much easier to use.)

Also and/or meanwhile, could you test in Firefox's Safe Mode? That temporarily deactivates extensions, hardware acceleration, and some other advanced features of Firefox that might make it more prone to crashing on some systems.

If Firefox is not running: Hold down the option/alt key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any less crashy?

noremacniai
noremacniai Biabia la
more options

Hi jscher2000, Many thanks for your time/effort/feedback. You're right about it having nothing to do with updates - Either Firefox or Apple or anything - It just started out of a clear blue sky - This is the crash report - https://crash-stats.mozilla.com/report/index/bp-205c99e7-463f-4da1-9c88-8d0640181121

I'll try Safe Mode but it doesn't happen with enough frequency to be sure.

Many thanks, noremacniai

noremacniai trɔe