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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/66a7a37669a359059140065d35dc324191f85ab8 (Reland "Share one GLContext for all RasterDecoder when virtual context is used.").

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/+/bcc56e24c4d04ef9e43882ca93a0c35de04e9033

commit bcc56e24c4d04ef9e43882ca93a0c35de04e9033
Author: Peng Huang <penghuang@chromium.org>
Date: Sat Dec 08 12:29:58 2018

Fix a DCHECK crash within fuzzer test

TBR=piman@chromium.org

Bug:  913172 
Change-Id: I12f00caedd7be4641be7f72baa85a5b7992920ad
Reviewed-on: https://chromium-review.googlesource.com/c/1369140
Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#614969}
[modify] https://crrev.com/bcc56e24c4d04ef9e43882ca93a0c35de04e9033/gpu/command_buffer/tests/fuzzer_main.cc

ClusterFuzz has detected this issue as fixed in range 614968:614969.

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

Fuzzer: libFuzzer_gpu_raster_angle_fuzzer
Fuzz target binary: gpu_raster_angle_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  context.get() == raster_decoder_context_state_->context() in raster_decoder.cc
  gpu::raster::RasterDecoderImpl::Initialize
  gpu::CommandBufferSetup::InitDecoder
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=614792:614796
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=614968:614969

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

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

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