providing findit results for internal purpose:

Suspected CLs	No CL in the regression range changes the crashed files. The result is the blame information.

Author: bsalomon
Project: chromium-skia
Changelist: https://chromium.googlesource.com/skia.git/+/84a4e5a8d683bf17d6c3058b977b9dfb000428af
Time: Mon Feb 29 19:41:52 2016
The CL last changed line 193 of file SkImage.cpp, which is stack frame 0.

Author: junov
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src//+/0090816b130a929829e025a2386e23228983e058
Time: Fri Feb 12 18:20:34 2016
The CL last changed line 35 of file ImageBitmapRenderingContext.cpp, which is stack frame 1.

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

unable to find exact culprit, assigning to skia team (https://cs.chromium.org/chromium/src/third_party/skia/OWNERS)

reed@; bsalomon@ - Could you please take a look at the issue and assign it to concerned developer if your changes are not responsible?

ClusterFuzz has detected this issue as fixed in range 405116:405163.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4719980688179200

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  SkImage::isTextureBacked
  blink::ImageBitmapRenderingContext::transferFromImageBitmap
  blink::ImageBitmapRenderingContextV8Internal::transferFromImageBitmapMethodCallb
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=395055:395067
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=405116:405163

Minimized Testcase (0.35 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv969x32AFC2XrDpNVI0P90T9CKMF3aBryivxwP3bfbwx_5g8Ff3l9FUISi1xszaJjusglZDFN08z8nHrIo2hmG1Tj0dN5-nfL-Yn_z_1Nfzn57BueFzaY4YOBewzoWT7W2SNyV-wz0My9CkNgGIxD-lMtu2uLg?testcase_id=4719980688179200
<canvas id="output">
  <script>
__v_5 = 102;
__v_4 = 100;
__v_0 = new OffscreenCanvas(__v_5, __v_4);
var __v_6 = __v_0.getContext('webgl');
__v_1 = __v_0.transferToImageBitmap();
__v_1 = __v_0.transferToImageBitmap();
__v_3 = document.getElementById("output");
__v_2 = __v_3.getContext('bitmaprenderer');
__v_2.transferFromImageBitmap(__v_1);
  </script>


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 is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the 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