Breakpoint in blink::LayoutListItem::UpdateListMarkerNumbers |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4662048930922496 Fuzzer: ifratric-browserfuzzer-v3 Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Breakpoint Crash Address: 0xf69c1880 Crash State: blink::LayoutListItem::UpdateListMarkerNumbers blink::LayoutObjectChildList::RemoveChildNode blink::LayoutObject::RemoveChild Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=502912:502960 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4662048930922496 Additional requirements: Requires Gestures Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 28 2017
Was an intentional change to crash instead of causing a security problem.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 4 2017
ClusterFuzz testcase 4662048930922496 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 7 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pnangunoori@chromium.org
, Sep 20 2017Labels: M-63 Test-Predator-Wrong
Owner: e...@chromium.org
Status: Assigned (was: Untriaged)