Closed
Bug 1234760
Opened 9 years ago
Closed 7 years ago
EXCEPTION_ACCESS_VIOLATION_READ in mozilla::a11y::Accessible::InvalidateChildrenGroupInfo
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sbracegirdle, Unassigned)
Details
(Keywords: crash)
Crash Data
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36 Steps to reproduce: Navigating within our privately hosted single-page application that makes several HTTP POST requests, selecting a particular tab causes the browser to crash. Actual results: Firefox crashed with reason "EXCEPTION_ACCESS_VIOLATION_READ" in "mozilla::a11y::Accessible::InvalidateChildrenGroupInfo". Full crash report: https://crash-stats.mozilla.com/report/index/f245a220-fc32-43db-ba5a-7d1702151223 Observed across several devices (mostly Microsoft Surface 3, Microsoft Surface Pro 3 and Microsft Surface Pro 4 hardware), all running Windows 10. Issue reproduced in Firefox versions 43.0.2 and 43.0.1. Expected results: Not crashing
Severity: normal → critical
Crash Signature: [@ mozilla::a11y::Accessible::InvalidateChildrenGroupInfo ]
Component: Untriaged → Disability Access APIs
Keywords: crash
Product: Firefox → Core
Comment 1•8 years ago
|
||
(In reply to sbracegirdle from comment #0) > User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like > Gecko) Chrome/47.0.2526.73 Safari/537.36 > > Steps to reproduce: > > Navigating within our privately hosted single-page application that makes > several HTTP POST requests, selecting a particular tab causes the browser to > crash. could you please try to come up with some sort of publishable test case?
Comment 2•7 years ago
|
||
Thanks for filing this. I think this crash signature went away in Firefox 46.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•