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

Issue 799066 link

Starred by 1 user
Status: Verified
Owner:
futhark@chromium.org
Closed: Jan 2018
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Null-dereference READ in blink::LayoutBlock::AddChildBeforeDescendant

Project Member Reported by ClusterFuzz, Jan 4 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5838523847671808

Fuzzer: mbarbella_webcomponents
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::LayoutBlock::AddChildBeforeDescendant
  blink::LayoutTreeBuilderForElement::CreateLayoutObject
  blink::Element::AttachLayoutTree
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=526968:526970

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Jan 5 2018

Cc: brajkumar@chromium.org
Components: Blink>DOM Blink>Layout
Labels: -Type-Bug M-65 Test-Predator-Wrong Type-Bug-Regression
Owner: futhark@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "LayoutBlock.cpp" assigning to the concern owner who might be related.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/fc5c3629044888b8d723cc11424879bb883d8d3e

futhark@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 2 by futhark@chromium.org, Jan 5 2018

Status: Fixed (was: Assigned)
Offending CL has been reverted.
Project Member

Comment 3 by ClusterFuzz, Feb 2 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 5838523847671808 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment