Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: Geoff Lang
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f44323edbf586dc2077aad835da9aec7bc3e5f26
Time: Wed Jun 07 18:10:15 2017
Lines 311-314 of file gl_utils.cc which potentially caused crash are changed in this cl (frame #10, "gpu::gles2::GetContextLostReasonFromResetStatus").

@ geofflang: Assigning to you, kindly take a look into it. Please help us to find an owner if not with respect to your change.

Thanks.!

ClusterFuzz has detected this issue as fixed in range 479081:479187.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in gl_utils.cc
  base::debug::DebugBreak
  gpu::gles2::GetContextLostReasonFromResetStatus
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=477699:477743
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=479081:479187

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


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

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