1822811 - macOS Crash in [@ mozilla::a11y::LegacyTextMarkerRange::Length]

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

For 112.0b1 and 112.0b3, there are 80 crash reports from 30 installations.

Crash report: https://crash-stats.mozilla.org/report/index/28da3faf-7bc8-4515-a0ad-a1a250230316

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0  XUL  mozilla::a11y::LegacyTextMarkerRange::Length const  accessible/mac/LegacyTextMarker.mm:317
1  XUL  mozilla::a11y::GeckoTextMarkerRange::Length const  accessible/mac/GeckoTextMarker.h:186
1  XUL  -[MOXTextMarkerDelegate moxLengthForTextMarkerRange:]  accessible/mac/MOXTextMarkerDelegate.mm:259
2  XUL  -[MOXAccessibleBase accessibilityAttributeValue:forParameter:]  accessible/mac/MOXAccessibleBase.mm:359
3  AppKit  ___NSAccessibilityEntryPointValueForAttributeWithParameter_block_invoke.849  
4  AppKit  NSAccessibilityPerformEntryPointObject  
5  AppKit  NSAccessibilityEntryPointValueForAttributeWithParameter  
6  AppKit  CopyParameterizedAttributeValue  
7  HIServices  _AXXMIGCopyParameterizedAttributeValue  
8  HIServices  _XCopyParameterizedAttributeValue  

Comment 1

[Eitan Isaacson [:eeejay]]

I think the fix in bug 1822544 will fix this too.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 desktop browser crashes on Mac on beta

:Jamie, could you consider increasing the severity of this top-crash bug?

For more information, please visit auto_nag documentation.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The bug is marked as tracked for firefox112 (beta) and tracked for firefox113 (nightly). However, the bug still isn't assigned.

:fgriffith, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit auto_nag documentation.

Comment 4

[James Teh [:Jamie]]

Assigning to Eitan to stop the bot from complaining, but hopefully we can just close this once we have enough data to verify that it's fixed by bug 1822544.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

No crashes from 112.0b5.