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://chromium.googlesource.com/chromium/src/+/4c5bf9d6c03db357cf4388790132e5d60bb9b3dc (Explicitly manage mips in GPU Image Decode Cache.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

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

commit 3da670e5f505e98bc743f1fcf948b3f9615f9d8d
Author: Eric Karl <ericrk@chromium.org>
Date: Mon Jul 16 18:07:17 2018

Add alignment to ImageTransferCacheEntry data

Data pointer must be 4-byte aligned for mipmap generation to succeed,
add an alignment call to ensure this is always the case.

Bug:  863659 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I64c3806c1d1bfcd34fff48baedc5abfc8fb37ef4
Reviewed-on: https://chromium-review.googlesource.com/1137922
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575346}
[modify] https://crrev.com/3da670e5f505e98bc743f1fcf948b3f9615f9d8d/cc/paint/image_transfer_cache_entry.cc

ClusterFuzz has detected this issue as fixed in range 575340:575347.

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

Fuzzer: libFuzzer_transfer_cache_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  SkIsAlign4(reinterpret_cast<uintptr_t>(pixel_data)) in image_transfer_cache_entr
  cc::ServiceImageTransferCacheEntry::Deserialize
  transfer_cache_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=574860:574862
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=575340:575347

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5247644717547520 is verified as fixed, so closing issue as verified.

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