New issue
Advanced search Search tips

Issue 873741 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Float-cast-overflow in Blend

Project Member Reported by ClusterFuzz, Aug 13

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  Blend
  blink::Length::BlendSameTypes
  blink::Length::Blend
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551565:563900

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Aug 13

Components: 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.
Cc: kkaluri@chromium.org f...@opera.com
Labels: M-69 Test-Predator-Wrong
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "translate_transform_operation.cc" suspecting the below Cl might have caused this issue

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

Since author is not chromium member, assigning it to reviewer

schenney@ -- 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!
Cc: -f...@opera.com schenney@chromium.org
Owner: f...@opera.com
fs@, I would lean toward not fixing, but feel free to have a look. I believe if you own the bug you can see the test case.
Components: -Platform Blink>Paint
I haven't minimized the TC yet, but looking at it a bit it would seem that this is caused by the |progress| value being large (passed in through Element.animate().)

Sign in to add a comment