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

Issue 852734 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !std::isnan(static_cast<double>(value)) in math_extras.h

Project Member Reported by ClusterFuzz, Jun 14 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_debug_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !std::isnan(static_cast<double>(value)) in math_extras.h
  int clampTo<int, float>
  blink::RoundedIntPoint
  
Sanitizer: address (ASAN)

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

Additional requirements: Requires HTTP

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: brajkumar@chromium.org
Components: Blink
Labels: M-69 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!

Comment 2 by bokan@chromium.org, Jun 19 2018

Components: -Blink Blink>Layout
Project Member

Comment 3 by ClusterFuzz, Jun 20 2018

Components: Blink>Internals>WTF Platform
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 4 by yutak@chromium.org, Jun 21 2018

Components: -Platform -Blink>Internals>WTF
Labels: Test-Predator-Wrong-Components

Comment 5 by e...@chromium.org, Jun 28 2018

Status: WontFix (was: Untriaged)
Project Member

Comment 6 by ClusterFuzz, Jul 5

Labels: Needs-Feedback
ClusterFuzz testcase 5589565168156672 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Sign in to add a comment