Closed Bug 1825504 Opened 3 years ago Closed 1 year ago

Crash in [@ mozilla::a11y::RemoteAccessibleBase<T>::RemoteParent]

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/b6330899-13e2-48e7-8e33-61a2e0230330

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0  libxul.so  PLDHashTable::EntryStore::IsAllocated const  xpcom/ds/PLDHashTable.h:325
0  libxul.so  PLDHashTable::Search const  xpcom/ds/PLDHashTable.cpp:496
1  libxul.so  mozilla::a11y::RemoteAccessibleBase<mozilla::a11y::RemoteAccessible>::RemoteParent const  accessible/ipc/RemoteAccessibleBase.cpp
2  libxul.so  mozilla::a11y::RemoteAccessibleBase<mozilla::a11y::RemoteAccessible>::ApplyCrossDocOffset const  accessible/ipc/RemoteAccessibleBase.cpp:466
3  libxul.so  mozilla::a11y::RemoteAccessibleBase<mozilla::a11y::RemoteAccessible>::BoundsWithOffset const  accessible/ipc/RemoteAccessibleBase.cpp:607
4  libxul.so  mozilla::a11y::RemoteAccessibleBase<mozilla::a11y::RemoteAccessible>::Bounds const  accessible/ipc/RemoteAccessibleBase.cpp:668
5  libxul.so  mozilla::a11y::RemoteAccessible::Bounds const  accessible/ipc/other/RemoteAccessible.cpp:935
6  libxul.so  mozilla::a11y::SessionAccessibility::PopulateNodeInfo  accessible/android/SessionAccessibility.cpp:875
7  libxul.so  mozilla::a11y::SessionAccessibility::GetNodeInfo  accessible/android/SessionAccessibility.cpp:140
7  libxul.so  mozilla::jni::detail::Accessor<mozilla::a11y::SessionAccessibility>::operator->*<void  const  widget/android/jni/Natives.h:722

This is a NULL pointer dereference, it's not 100% clear to me where it's happening though. It seems Android-specific. I'm putting in both the new and old crash signature.

Severity: -- → S3

Closing because no crashes reported for 12 weeks.

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