Closed Bug 1497883 Opened 6 years ago Closed 6 years ago

Crash in nsIDocument::GetRootElement

Categories

(Core :: Disability Access APIs, defect)

64 Branch
Unspecified
Android
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla64
Tracking Status
firefox-esr60 --- unaffected
firefox62 --- unaffected
firefox63 --- unaffected
firefox64 --- fixed

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is report bp-0232e477-fdc7-485a-b383-c17eb0181010. ============================================================= Top 10 frames of crashing thread: 0 libxul.so nsIDocument::GetRootElement const dom/base/nsDocument.cpp:4296 1 libxul.so nsIDocument::GetTitle dom/base/nsDocument.cpp:6399 2 libxul.so mozilla::a11y::DocAccessible::Name const accessible/generic/DocAccessible.cpp:186 3 libxul.so mozilla::a11y::AccessibleWrap::ToBundle accessible/android/AccessibleWrap.cpp:479 4 libxul.so nsAppShell::LambdaEvent<mozilla::a11y::SessionAccessibility::GetNodeInfo accessible/android/SessionAccessibility.cpp:82 5 libxul.so nsAppShell::LambdaEvent<nsAppShell::SyncRunEvent widget/android/nsAppShell.cpp:787 6 libxul.so nsAppShell::ProcessNextNativeEvent widget/android/nsAppShell.cpp:759 7 libxul.so nsBaseAppShell::DoProcessNextNativeEvent widget/nsBaseAppShell.cpp:140 8 libxul.so nsBaseAppShell::OnProcessNextEvent widget/nsBaseAppShell.cpp:273 9 libxul.so non-virtual thunk to nsBaseAppShell::OnProcessNextEvent widget/nsBaseAppShell.cpp ============================================================= There are 42 crashes (from 21 installations) in nightly 64 with buildid 20181010100126. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1479037. [1] https://hg.mozilla.org/mozilla-central/rev?node=630601f0663e
Flags: needinfo?(eitan)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Flags: needinfo?(eitan)
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.