Crash in blink::Node::unregisterMutationObserver |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5384560152150016 Fuzzer: inferno_twister Job Type: windows_asan_content_shell Platform Id: windows Crash Type: UNKNOWN READ Crash Address: 0x00000008 Crash State: blink::Node::unregisterMutationObserver blink::MutationObserverRegistration::unregister blink::MutationObserver::disconnect Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_content_shell&range=410785:410843 Minimized Testcase (9.43 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94vhCjGvs3pyP8NvgqJ3JSzQJRBeB8BfIjXHQbaUNJwhNrrpJSiXoo5bSqIjzFOZD2oRclVwlaYcApmHyvdFZfWUZjX25oK1B8EE1yehJrcrc-0OBP1SMpwHnsq6O5TEOKLDCXbMak1Vl_dvD5PooARWO1-gg?testcase_id=5384560152150016 Issue manually filed by: nyerramilli See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Aug 10 2016
Nothing jumped out from the regression range but I'm not sure I'd know. It looks to me like m_registrationNode is NULL in MutationObserverRegistration::unregister(). This is DCHECK'd but the ASAN build is release (I'm guessing with DCHECKs off). sigbjornf@ added this DCHECK so he may have a better sense of what's going wrong. Sigbjorn, could you please triage? Thanks.
,
Aug 10 2016
Windows version of issue 592322?
,
Aug 10 2016
Looks like it. Thanks Sigbjorn! According to issue 592322 this is flaky so the regression range shouldn't be trusted.
,
Oct 18 2016
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Aug 10 2016Components: Tools>Test>FindIt>WrongResult
Labels: findit-wrong Te-Logged
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)