Open Bug 1717501 Opened 3 months ago Updated 23 days ago

Crash in [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute]

Categories

(Core :: Disability Access APIs, defect)

x86_64
macOS
defect

Tracking

()

Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- unaffected
firefox89 --- unaffected
firefox90 --- unaffected
firefox91 --- affected

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash, Whiteboard: [not-a-fission-bug])

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/23c3c997-8a7a-4cc9-ba0e-eda380210615

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0 XUL PLDHashTable::Search const xpcom/ds/PLDHashTable.cpp:494
1 XUL mozilla::a11y::AccAttributes::GetAttribute accessible/base/AccAttributes.cpp:12
2 XUL mozilla::a11y::utils::GetAccAttr accessible/mac/MacUtils.mm:74
3 XUL -[mozAccessible moxRoleDescription] accessible/mac/mozAccessible.mm:534
4 XUL -[MOXAccessibleBase accessibilityAttributeValue:] accessible/mac/MOXAccessibleBase.mm:140
5 AppKit NSAccessibilityGetObjectForAttributeUsingLegacyAPI 
6 AppKit ___NSAccessibilityEntryPointValueForAttribute_block_invoke.805 
7 AppKit NSAccessibilityPerformEntryPointObject 
8 AppKit _NSAccessibilityEntryPointValueForAttribute 
9 AppKit -[NSObject _accessibilityValueForAttribute:clientError:] 

There aren't a ton of these crashes, but they are from more than one install date, and I figure there probably isn't a huge amount of people running Nightly on OSX with a11y. The stacks are a bit odd looking.

Severity: -- → S2

I see five crash reports from three different installations and all five crash reports have Fission enabled:

https://crash-stats.mozilla.org/signature/?signature=PLDHashTable%3A%3ASearch%20%7C%20mozilla%3A%3Aa11y%3A%3AAccAttributes%3A%3AGetAttribute&date=%3E%3D2020-12-25T19%3A05%3A00.000Z&date=%3C2021-06-25T19%3A05%3A00.000Z

Since almost 60% of Nightly users have Fission enabled, TBD whether this a11y crash is actually Fission-related.

Fission Milestone: --- → ?
Hardware: Unspecified → x86_64

kmag says this crash is probably not Fission related, so I will clear the Fission Milestone flag.

There have been no new crash reports after the first five reports from one user, so this crash is probably a low priority.

Fission Milestone: ? → ---
Whiteboard: [not-a-fission-bug]
You need to log in before you can comment on or make changes to this bug.