Author: mtklein
Project: chromium-skia
Changelist: https://chromium.googlesource.com/skia.git/+/343a63d082bda969d7e8a4e09ba850e931185269
Time: Tue Mar 22 18:46:53 2016
The CL last changed line 54 of file SkRecordDraw.cpp, which is stack frame 6.

Suspected Project: chromium-skia
Suspected Component: Internals>Skia

mtklein@, could you please take a look and please help us to find correct owner if it is not related your changes.

We can definitely rule that CL out.  It's a complete no-op refactor in terms of behavior... it should generate identical binary output.

Unable to find actual suspect for this issue, so marking it as available and adding Needs-triage label

SkRecordDraw.cpp file is not accessible, so assigning to owners of //src/third_party/skia/ the file.

reed@, could you please take a look and help us to find right owner for this issue.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ClusterFuzz has detected this issue as fixed in range 456626:457730.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  XRect_roundOut
  SkScan::AntiFillXRect
  aa_square_proc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=398502:398570
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=456626:457730

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv975mntPulcwCflDst79ZRqxIB9_n25Xq5d6EYU4f4PocVcZWpg4jVLsUacBtcjXP6HjYDRNToNC_sFR_0Ofaou4p8B1hdtOERq0mG2Tj3SYWMdXPuObq-iuCOkL0dqpyAj_ds9uj4Malc35yOa_lE0mjDXGpQ?testcase_id=6705463188258816


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

ClusterFuzz testcase 6705463188258816 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.