New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 766945 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Breakpoint in blink::LayoutListItem::UpdateListMarkerNumbers

Project Member Reported by ClusterFuzz, Sep 20 2017

Issue description

Detailed 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.
 
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Labels: M-63 Test-Predator-Wrong
Owner: e...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “LayoutObject.cpp” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/ea39d1dc3b628c867bb78baddbf44e2f017e0456

@eae -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 2 by e...@chromium.org, Sep 28 2017

Labels: -Pri-1 Pri-2
Owner: ----
Status: Available (was: Assigned)
Was an intentional change to crash instead of causing a security problem.
Project Member

Comment 3 by ClusterFuzz, Oct 1 2017

Components: Blink>Layout
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 4 by ClusterFuzz, Oct 4 2017

Status: WontFix (was: Available)
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.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Sign in to add a comment