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

Issue 769973 link

Starred by 1 user
Status: Duplicate
Owner:
█ msten...@opera.com
NOT IN USE
Closed: Sep 2017
Cc:
tkent@chromium.org
pnangunoori@chromium.org
█ msrchandra@chromium.org
haraken@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::Node::GetLayoutBox

Project Member Reported by ClusterFuzz, Sep 28 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5235949863960576

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::Node::GetLayoutBox
  blink::LayoutSlider::UpdateLayout
  blink::LayoutBlockFlow::PositionAndLayoutFloat
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=312742:312797

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5235949863960576

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Comment 1 by pnangunoori@chromium.org, Sep 29 2017

Cc: falken@chromium.org msrchandra@chromium.org pnangunoori@chromium.org
Components: Blink>Layout
Labels: M-62 Test-Predator-Wrong
Owner: msten...@opera.com
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “Node.cpp” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/cf172439200ba4acd6ed6c8ce53c7f46b2556aaa
@mstensho -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 2 by falken@chromium.org, Sep 29 2017

Cc: -falken@chromium.org tkent@chromium.org haraken@chromium.org
Mergedinto: 580734
Status: Duplicate (was: Assigned)
falken@ is not related to the commit in comment #1. (I was incorrectly CC'd on  issue 768361  also)
►

Sign in to add a comment