Closed Bug 1793126 Opened 4 years ago Closed 3 years ago

Crash in [@ mozilla::a11y::Accessible::IsLocal]

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 1791152
Tracking Status
firefox-esr102 --- unaffected
firefox105 --- unaffected
firefox106 --- wontfix
firefox107 --- fixed
firefox108 --- fixed

People

(Reporter: m_kato, Assigned: morgan)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 obsolete file)

This seems to be top 3 crash in Fenix Nightly.

Crash report: https://crash-stats.mozilla.org/report/index/2b49c828-fff4-4fd8-b66f-9dbf40220930

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxul.so mozilla::a11y::Accessible::IsLocal const accessible/basetypes/Accessible.h:556
0 libxul.so mozilla::a11y::AccessibleWrap::SetVirtualViewID accessible/android/AccessibleWrap.cpp:574
1 libxul.so mozilla::a11y::SessionAccessibility::UnregisterAll accessible/android/SessionAccessibility.cpp:1100
2 libxul.so mozilla::a11y::DocAccessibleWrap::Shutdown accessible/android/DocAccessibleWrap.cpp:57
3 libxul.so mozilla::a11y::DocManager::HandleEvent accessible/base/DocManager.cpp:361
4 libxul.so {virtual override thunk} accessible/base/DocManager.cpp
5 libxul.so mozilla::EventListenerManager::HandleEventSubType dom/events/EventListenerManager.cpp:1316
6 libxul.so mozilla::EventListenerManager::HandleEventInternal dom/events/EventListenerManager.cpp:1506
7 libxul.so mozilla::EventTargetChainItem::HandleEventTargetChain dom/events/EventDispatcher.cpp:480
8 libxul.so mozilla::EventDispatcher::Dispatch dom/events/EventDispatcher.cpp:1119

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

  • Top 10 AArch64 and ARM crashes on nightly

For more information, please visit auto_nag documentation.

Keywords: topcrash
Flags: needinfo?(eitan)

This looks like a regression in Fenix Nightly 107.0a1. The first crash report was from build ID 20220909093917, but I don't trust that 20220909093917 was the regressing build because there are a couple day gaps between early crash reports.

Regressed by: 1786584

Set release status flags based on info from the regressing bug 1786584

Assignee: nobody → mreschenberg
Status: NEW → ASSIGNED
Attachment #9301335 - Attachment is obsolete: true

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit auto_nag documentation.

Keywords: topcrash
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1791152
Flags: needinfo?(eitan)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: