Predator and CL did not provide any possible suspects.
Using Code Search for the file, "program_manager.cc", assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/ceb64f73f7bf1e1ae1914970c9adc455f564a1e9

@geofflang -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

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

commit cc462262940e863770555a7dba23072480d016df
Author: geofflang <geofflang@chromium.org>
Date: Mon Feb 06 21:52:46 2017

Check that the shader source exists before loading from the ProgramCache.

Now that the program cache is almost always created, the cache should only be
checked when the previously compile shader source exists.  This was hit by
the GPU fuzzer when testing without the program binary extensions enabled.

BUG= 688795 
BUG= 671217 
CQ_INCLUDE_TRYBOTS=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

Review-Url: https://codereview.chromium.org/2674263003
Cr-Commit-Position: refs/heads/master@{#448404}

[modify] https://crrev.com/cc462262940e863770555a7dba23072480d016df/gpu/command_buffer/service/program_manager.cc

ClusterFuzz has detected this issue as fixed in range 448360:448439.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6005891985047552

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_debug_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !attached_shaders_[0]->last_compiled_source().empty() && !attached_shaders_[1]->
  gpu::gles2::Program::Link
  gpu::gles2::GLES2DecoderImpl::DoLinkProgram
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=446721:447186
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=448360:448439

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94I7AQF6ffX2gDOCIFaw6uytk-8wCltlULyDJEUIaCCm43N80TFV8DtUjPENHE2TPOKlWgtVPayo0f4tkqaxgG0cmK7exCLLmR1RzZ7ZEGlALEc5C9b16lNiG-MlHQHFzGW7pPhaloKSRtpPpk5Zd608YnwBv78EmcxxMjuo2r58q8WxyZaqOPN5jwDvwhU-Ess3t8I9tcuC3ruhLuU77qHTbjKC_JnxFBS4PyN32w8XoP1-6JaqNU03YiiM2BhmAE3ilwMoIhW10eZaNU2fGMENqlSCWrn5fje9AVBRI4dwuLbw3v6f9ob1Xz9iNnRN5yk2JecuDLC49JIhXMfMkpw9A8N8O-nBOitosdW3ugeJHRYcZsA1hz3DacIYNvvBO0ACAu6M8ZJz938Mm0th7wNTJzFbQ?testcase_id=6005891985047552


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 6005891985047552 is verified as fixed, so closing issue.

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