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

Author: qiankun.miao
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/7ff451867f332a745a18fde712f091cb80e18548
Time: Mon Jan 09 11:29:24 2017
Lines 16550-16554 of file gles2_cmd_decoder.cc which potentially caused crash are changed in this cl (frame #5, "gpu::gles2::GLES2DecoderImpl::DoCopySubTextureCHROMIUM").
Minimum distance from crash line to modified line: 0. (file: gles2_cmd_decoder.cc, crashed on: 16550, modified: 16550).

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

I am looking at it with high priority.

ClusterFuzz has detected this issue as fixed in range 444280:444427.

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

Fuzzer: libfuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e9000011c7
Crash State:
  base::debug::DebugBreak
  gpu::gles2::GLES2DecoderImpl::DoCopySubTextureCHROMIUM
  gpu::gles2::GLES2DecoderImpl::HandleCopySubTextureCHROMIUM
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=442226:442234
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=444280:444427

Minimized Testcase (0.07 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95eCTK-JaNgi3LZGSffZ3Ddfh4SGdNgWb6BzUD6txm1GowdTDgQ1XF7twBhgzIeXWgCHLrQCXICsVSM91e7A9mDomL_VUN1Sztrnskror4bLg4jcJrB8VNH_iLuZdvgrV5-1mJWYdXUM_hsQd74S17LCZXeJOBp6SJ7bIUgtBBq0UNtd4yLwjblX_Nm6-t2tb-ctng6oMxU8Vz9YewkDLhaauayIT0gjUgKTJh6wmBFUss1Ii1a5t69ElVzhayhMUFcS0JlJQdIGYYCx0Yjgp5MthQuxsHcD24JypVV5y7BKKnh5VbiVzXhL1SfZGQ0NjrM05YX2sfT_twNmfs1OiaJUxQxKlNL38ApBIttd26_T0fzI1fQRpj6BQH2CVDxJpLzBxP1FNpNE0yaMNZYtLdtcNgsFQ?testcase_id=5412874932715520

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

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