Closed
Bug 1583045
Opened 6 years ago
Closed 6 years ago
Crash in [@ mozilla::a11y::Accessible::RelocateChild]
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1578185
People
(Reporter: jseward, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-edb708d8-8828-461c-8110-b52720190921.
This crash appeared 4 times in 4 different installations in the Windows nightly of 20190919184237.
Top 10 frames of crashing thread:
0 xul.dll mozilla::a11y::Accessible::RelocateChild accessible/generic/Accessible.cpp:2218
1 xul.dll bool mozilla::a11y::DocAccessible::MoveChild accessible/generic/DocAccessible.cpp:2327
2 xul.dll mozilla::a11y::DocAccessible::ProcessContentInserted accessible/generic/DocAccessible.cpp:1936
3 xul.dll void mozilla::a11y::NotificationController::WillRefresh accessible/base/NotificationController.cpp:743
4 xul.dll void nsRefreshDriver::Tick layout/base/nsRefreshDriver.cpp:1928
5 xul.dll void mozilla::RefreshDriverTimer::TickRefreshDrivers layout/base/nsRefreshDriver.cpp:350
6 xul.dll void mozilla::RefreshDriverTimer::Tick layout/base/nsRefreshDriver.cpp:367
7 xul.dll void mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::TickRefreshDriver layout/base/nsRefreshDriver.cpp:727
8 xul.dll bool mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsync layout/base/nsRefreshDriver.cpp:622
9 xul.dll mozilla::layout::PVsyncChild::OnMessageReceived ipc/ipdl/PVsyncChild.cpp:187
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(jteh)
Comment 1•6 years ago
|
||
Redirecting to Eitan, since this is probably in his bucket, either another regression from bug 686400, or one from fixing fallout of this. I haven't seen this myself, though.
Flags: needinfo?(jteh) → needinfo?(eitan)
Comment 2•6 years ago
|
||
This is actually the same as bug 1578185. This particular overload of MoveChild got renamed to RelocateChild in bug 1578416.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(eitan)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•