Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://skia.googlesource.com/skia/+/914a36b248ffb538874483d86759254838866dd7 (MakeBackendTextureFromSkImage).

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

I'll take this.

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

commit 985e9443e23940d15fcad2accfab741156239a8c
Author: Justin Novosad <junov@chromium.org>
Date: Mon Nov 06 19:26:43 2017

Fix crash due to allocation failure in CreateImageBitmap

BUG= 781175 

Change-Id: If8b1a100b41e5bde7035def350c92abb18e9f0a6
Reviewed-on: https://chromium-review.googlesource.com/753922
Commit-Queue: Justin Novosad <junov@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514208}
[modify] https://crrev.com/985e9443e23940d15fcad2accfab741156239a8c/third_party/WebKit/Source/core/imagebitmap/ImageBitmap.cpp

ClusterFuzz has detected this issue as fixed in range 514186:514212.

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

Fuzzer: inferno_layout_test_fuzzer
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  SkSurface_Base::getCachedCanvas
  blink::ImageBitmap::RasterizeImageOnBackgroundThread
  void base::internal::FunctorTraits<void
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=508795:508862
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=514186:514212

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

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.

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

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