New issue
Advanced search Search tips

Issue 807429 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Jan 30 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5072208434298880

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::Node::GetLayoutBox
  blink::LayoutSlider::UpdateLayout
  blink::LayoutBlockFlow::PositionAndLayoutOnceIfNeeded
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=518240:518474

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jan 30 2018

Components: Blink>DOM Blink>Layout
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jan 30 2018

Cc: mustaq@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

No EventDispatchMediator is the best EventDispatchMediator! by mustaq@google.com - https://chromium.googlesource.com/chromium/src/+/dd36316add75b494525eab19b86e4fa165f85fca

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by rakina@chromium.org, Jan 31 2018

Labels: -Pri-1 Pri-2
Status: Available (was: Untriaged)
Labels: Test-Predator-Wrong-CLs
The CL mentioned above is unrelated: the CL only affects DOM event dispatching, and the stack-trace shows of the crash has not event-related function calls.  Instead, the stack-trace seems to suggest a problem with layout (specifically in layout/Layout*).
Cc: kojii@chromium.org f...@opera.com szager@chromium.org
cc-ing authors of layout-related changes in the range:
https://chromium.googlesource.com/chromium/src/+log/9d2bc3eaf729a97bab085062151676e5e8a374a3..d2d6ee9c44327d3f4518dbc904f8c7d4aa4128af?pretty=fuller&n=10000

Comment 6 by kojii@chromium.org, Feb 5 2018

Cc: tkent@chromium.org
Components: -Blink>Layout -Blink>DOM Blink>Forms
Status: WontFix (was: Available)
The test modifies inside of UA shadow using internals.ShadowRoot(). I don't think this is possible for regular Chromium to run, closing as WontFix.

/cc tkent@, forms owner in case he has different opinion.

Comment 7 by tkent@chromium.org, Feb 6 2018

Mergedinto: 580734
Status: Duplicate (was: WontFix)
 Issue 810044  has been merged into this issue.

Sign in to add a comment