Using the provided regression range assigning to the possible suspect as per the change made for the file, “fuzzer_main.cc”
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/1a72ba63243487773d433c75541a19098cce5d07
https://chromium.googlesource.com/chromium/src/+/be517f416b88fe70ddf6060f6049cfba44497078

@piman -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Fuzzers were broken for a bit (  crbug.com/776267  ), and this likely regressed in the mean time, so my fix (https://chromium.googlesource.com/chromium/src/+/1a72ba63243487773d433c75541a19098cce5d07) uncovered the issue. I'll take a look.

https://chromium-review.googlesource.com/c/chromium/src/+/742226 should fix this.

 Issue 778997  has been merged into this issue.

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

commit 209944ffac5dd304580f855c29bcf2ef551b98d2
Author: Antoine Labour <piman@chromium.org>
Date: Mon Oct 30 17:30:47 2017

Fix gpu_angle_passthrough_fuzzer

https://chromium-review.googlesource.com/726403 accidentally lost a line
that sets recreate_context_ for passthrough command buffer. This
restores it.

Bug:  778911 
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ib5890c6015df014baf72fb2e7f5f55dcfaa78a15
Reviewed-on: https://chromium-review.googlesource.com/742226
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#512523}
[modify] https://crrev.com/209944ffac5dd304580f855c29bcf2ef551b98d2/gpu/command_buffer/tests/fuzzer_main.cc

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

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

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

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

ClusterFuzz has detected this issue as fixed in range 512867:512894.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result == gpu::ContextResult::kSuccess in fuzzer_main.cc
  gpu::CommandBufferSetup::InitDecoder
  gpu::CommandBufferSetup::RunCommandBuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=511274:511297
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=512867:512894

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

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.