Closed
Bug 1408239
Opened 8 years ago
Closed 4 years ago
stack-overflow in [@ mozilla::a11y::LinkableAccessible::ActionWalk]
Categories
(Core :: Disability Access APIs, defect, P2)
Core
Disability Access APIs
Tracking
()
People
(Reporter: tsmith, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: crash, testcase, Whiteboard: a11y:crash-tree:aria-owns)
Attachments
(2 files)
The stack contains the following frames repeating:
LinkState /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/a11y/Accessible.h:281:22
mozilla::a11y::LinkableAccessible::ActionWalk(bool*, bool*, bool*) /builds/worker/workspace/build/src/accessible/generic/BaseAccessibles.cpp:148
mozilla::a11y::LinkableAccessible::NativeLinkState() const /builds/worker/workspace/build/src/accessible/generic/BaseAccessibles.cpp:89:44
Flags: in-testsuite?
Reporter | ||
Comment 1•8 years ago
|
||
Comment 3•8 years ago
|
||
I can't get this to crash with a stack overflow (not using ASAN builds here), but I can at least reproduce a pegged CPU in the content process that loads the testcase. That issue goes back well into last year, though, so I don't think this is a recent regression.
Has Regression Range: --- → no
status-firefox56:
--- → wontfix
status-firefox57:
--- → wontfix
status-firefox-esr52:
--- → wontfix
Comment 4•8 years ago
|
||
I'm pretty convinced this is a dup of bug 1387308.
![]() |
||
Updated•8 years ago
|
Priority: -- → P2
Comment 5•7 years ago
|
||
status-firefox59:
--- → ?
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(twsmith)
Updated•7 years ago
|
Whiteboard: a11y:crash-tree:aria-owns
Reporter | ||
Updated•7 years ago
|
![]() |
||
Comment 6•4 years ago
|
||
Hey Tyson,
Can you still reproduce this issue or should we close it?
Flags: needinfo?(twsmith)
Reporter | ||
Comment 7•4 years ago
|
||
I cannot reproduce this issue with the attached test case and it was last reported by fuzzer against m-c 20191022-a8089b1fa5c4.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(twsmith)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•