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

Issue 813558 link

Starred by 1 user
Status: Verified
Owner:
█ trchen@chromium.org
Last visit > 30 days ago
Closed: Feb 2018
Cc:
█ trchen@chromium.org
ifratric@google.com
█ brajkumar@chromium.org
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::FragmentData::ClipPathProperties

Project Member Reported by ClusterFuzz, Feb 19 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4799123862323200

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  blink::FragmentData::ClipPathProperties
  blink::ClipPathClipper::~ClipPathClipper
  base::internal::OptionalBase<blink::ClipPathClipper>::FreeIfNeeded
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=537453:537464

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 19 2018

Components: Blink>Paint Internals>Core
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.

Comment 2 by schenney@chromium.org, Feb 20 2018

Cc: trchen@chromium.org
Components: -Internals>Core
Labels: -Pri-1 Pri-2
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
Null reads not P1. Assigning to chrishtr@ for first pass, but might be better for trchen@.

Comment 3 by brajkumar@chromium.org, Feb 22 2018

Cc: brajkumar@chromium.org
 Issue 813736  has been merged into this issue.

Comment 4 by chrishtr@google.com, Feb 24 2018

Owner: trchen@chromium.org
I can't reproduce this in a debug build. clusterfuzz reports the same (flaky repro).
Therefore not P1-critical, like Stephen said. Sending to you Tien-Ren.
Project Member

Comment 5 by ClusterFuzz, Feb 27 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5208366599897088 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