New issue
Advanced search Search tips

Issue 795604 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Floating-point-exception in blink::CanvasRenderingContext2D::GetControlAndIdIfHitRegionExists

Project Member Reported by ClusterFuzz, Dec 17 2017

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Floating-point-exception
Crash Address: 
Crash State:
  blink::CanvasRenderingContext2D::GetControlAndIdIfHitRegionExists
  blink::HTMLCanvasElement::GetControlAndIdIfHitRegionExists
  blink::PointerEventManager::ComputePointerEventTarget
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=380858:380870

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 17 2017

Components: Blink>Canvas Blink>HTML
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, Dec 17 2017

Labels: Test-Predator-Auto-Owner
Owner: jinho.b...@samsung.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f18571e9097d0533f6fc18d62b3ab006e1d6c6d4 (Canvas2d: Implement rerouting event by hit region's control.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Comment 3 by tkent@chromium.org, Jan 9 2018

Components: -Blink>HTML
Project Member

Comment 4 by bugdroid1@chromium.org, Feb 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2c1d42f7e5058b167f557d61b110280c14eb1dfa

commit 2c1d42f7e5058b167f557d61b110280c14eb1dfa
Author: Jinho Bang <jinho.bang@samsung.com>
Date: Thu Feb 22 18:17:16 2018

Canvas2d: Fix clusterfuzz crash

It's caused due to divide by zero during calculating region's position.

Bug:  795604 
Change-Id: Ibb1f43c6dea64549b9ca8e568d6dace4420fdf91
Reviewed-on: https://chromium-review.googlesource.com/893238
Reviewed-by: Justin Novosad <junov@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#538487}
[modify] https://crrev.com/2c1d42f7e5058b167f557d61b110280c14eb1dfa/third_party/WebKit/LayoutTests/fast/canvas-api/canvas-hit-regions-css-transform-test.html
[modify] https://crrev.com/2c1d42f7e5058b167f557d61b110280c14eb1dfa/third_party/WebKit/Source/modules/canvas/canvas2d/CanvasRenderingContext2D.cpp

Status: Fixed (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, Feb 23 2018

ClusterFuzz has detected this issue as fixed in range 538486:538490.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Floating-point-exception
Crash Address: 
Crash State:
  blink::CanvasRenderingContext2D::GetControlAndIdIfHitRegionExists
  blink::HTMLCanvasElement::GetControlAndIdIfHitRegionExists
  blink::PointerEventManager::ComputePointerEventTarget
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=380858:380870
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=538486:538490

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, Feb 23 2018

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