Predator and CL could not provide any possible suspects.
Using Code Search for the file, "libGLESv2_swiftshader" assigning to the concern owner who might be related.

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

Sorry I was OOO. I'm not an owner of that. Assigning to an OWNER of gpu/command_buffer

 Issue 763351  has been merged into this issue.

Alexis, this looks like another issue that started after enabling WebGL 2 support for SwiftShader. Please have a look.

Side note, would it make sense to exercise that path in gpu_fuzzer_swiftshader? Right now it uses CONTEXT_TYPE_OPENGLES2 for SwiftShader, but if it's now capable of ES3, we should switch to that like other gpu fuzzers (native GL, angle). It could give slightly more actionable bugs.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Fixed in SwiftShader here:
https://swiftshader-review.googlesource.com/#/c/SwiftShader/+/12648/

Will be in next DEPS roll.

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

commit 5955bc576d147925fb8966ca7b91a23f7c91591e
Author: Alexis Hetu <sugoi@google.com>
Date: Wed Oct 04 01:03:13 2017

Roll SwiftShader bc6ce4f..9d56da2

https://swiftshader.googlesource.com/SwiftShader.git/+log/bc6ce4f..9d56da2

BUG= chromium:763382 , chromium:763384 , chromium:763435 , chromium:765094 , chromium:765791 , chromium:765939 

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Idd52bdc26eba54615838baf5dc65705a8a4be631
Reviewed-on: https://chromium-review.googlesource.com/699156
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506259}
[modify] https://crrev.com/5955bc576d147925fb8966ca7b91a23f7c91591e/DEPS

ClusterFuzz has detected this issue as fixed in range 506256:506287.

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

Fuzzer: inferno_twister_c
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Divide-by-zero
Crash Address: 0x2c3df7c0
Crash State:
  libGLESv2_swiftshader
  Ordinal298
  Ordinal298
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=500372:500415
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=506256:506287

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

See https://github.com/google/clusterfuzz-tools 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 5081168717545472 is verified as fixed, so closing issue as verified.

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