Closed Bug 1541007 Opened 5 years ago Closed 5 years ago

Crash in [@ libobjc.A.dylib@0xffb0]

Categories

(Firefox :: Disability Access, defect, P3)

67 Branch
All
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox67 --- affected

People

(Reporter: asoncutean, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-d3832368-3aea-4222-9620-dad0b0190402.

Top 10 frames of crashing thread:

0 libobjc.A.dylib libobjc.A.dylib@0xffb0 
1 CoreFoundation CoreFoundation@0xddead 
2 CoreFoundation CoreFoundation@0x8070b 
3 CoreFoundation CoreFoundation@0x72814 
4 CoreFoundation CoreFoundation@0x71ff3 
5 CoreFoundation CoreFoundation@0x719f7 
6 HIToolbox HIToolbox@0x3256e 
7 HIToolbox HIToolbox@0x321ed 
8 HIToolbox HIToolbox@0x3212a 
9 AppKit AppKit@0x918aa 

[Steps to reproduce]:

  1. Launch Firefox and use the profile for a while
  2. Go to System Preferences -> Accessibility -> Display -> Activate "Increase Contrast"

[Actual result]:

  • The Firefox crashes the moment I click on the "Increase Contrast" button

[Notes]:

  • I encountered this crash only one time
  • The profile in cause has a lot of bookmarks/history and several customized items.
  • I am not sure if this is the right component, feel free to change it.
Component: General → Disability Access APIs
Product: Firefox → Core

The priority flag is not set for this bug.
:Jamie, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jteh)

This isn't related to accessibility APIs (as used by screen readers, etc.), since accessibility doesn't show as enabled for these crashes. Given that this is related to increased contrast, I'm moving this to Disability Access, though it should be moved to layout, graphics, etc. once we figure out exactly where the issue lies in the code. P3 because very low volume crash.

Component: Disability Access APIs → Disability Access
Flags: needinfo?(jteh)
Priority: -- → P3
Product: Core → Firefox

No recent crashes in this signature. It appears the most recent ones happened in 67.0b7 a few months ago. Resolving this one as WFM.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.