From above Change Log suspecting the below:
Review-Url: https://codereview.chromium.org/2693653002
dongseong.hwang@ : Could you please take a look into this if its related to your change.

Doesn't look related to dongseong.hwang's change. I'll investigate this on Monday.

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

commit 87b070a02a9413d0b48fd7ebd0d1c271c2f657c5
Author: kainino <kainino@chromium.org>
Date: Tue Mar 14 03:28:14 2017

Check for invalid dimensions in glTexStorage*

width, height, or depth of 0 are invalid for glTexStorage, but valid for
most other texture entry points, so this case wasn't covered by
TextureManager::ValidForTarget.

BUG= 700270 
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

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

[modify] https://crrev.com/87b070a02a9413d0b48fd7ebd0d1c271c2f657c5/gpu/command_buffer/service/gles2_cmd_decoder.cc
[modify] https://crrev.com/87b070a02a9413d0b48fd7ebd0d1c271c2f657c5/gpu/command_buffer/service/gles2_cmd_decoder_unittest_textures.cc

ClusterFuzz has detected this issue as fixed in range 456601:456622.

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

Fuzzer: libfuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  glGetError() == GL_NO_ERROR in feature_info.cc
  gpu::gles2::IsGL_REDSupportedOnFBOs
  gpu::gles2::FeatureInfo::InitializeFeatures
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=456601:456622

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97ds7W2iqDmxvJnrur3IPSQzrOqao1UCUCgs5KAO9b1dP28YJy84V6tGB9eww1JV9OG1KXPbbKd9QgmDRBBntSMkFXhzltMlTIpXjyOtPfZy5zwFeQOUiZ1b2sNPtwJJlMyzyYvC1wq40qoUq9C7SI4MBq8vkI5mMMohettOlXO2T9MjJSM1PmPMh0ofBhegKrJqJRt0GoJnJTgd7b9Xg_pzrWNGQV0Zm_fnrGMrVFIOtI7ZgSeGU6TwLoZX6j3O_gd5OC0hngzfGYmOGTgqcMHEGRGIYaL67qjvmKnQwimrifFg-CIYsbKzfnWixXIbCCF_LCWOXcwsF8aZlL14Zh77E62jzAAyfcaEmW6B8Ru8W4OEIw?testcase_id=5813044681900032


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

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