This is coming from our new shiny gce bots with nvidia gpus. (tesla-p100)

TextureD3D_2D::CopyImage clear using initializeContents by cwallez@chromium.org
Suspected changelist touched the crashing line in TextureD3D.cpp
Suspected changelist touched file(s) in the directories src/libANGLE, src/libANGLE/renderer/d3d, which appear in the stack trace.
Suspected changelist touched file TextureD3D.cpp, which appears in the stack trace.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ClusterFuzz has detected this issue as fixed in range 552146:552148.

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

Fuzzer: webDEViL_webgl
Job Type: windows_asan_chrome_with_gpu
Platform Id: windows

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x1176094a1280
Crash State:
  angle::LoadLA8ToRGBA8
  rx::Image11::loadData
  rx::TextureD3D::initializeContents
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552146:552148

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

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

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

ClusterFuzz has detected this issue as fixed in range 552581:552589.

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

Fuzzer: webDEViL_webgl
Job Type: windows_asan_chrome_with_gpu
Platform Id: windows

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x1176094a1280
Crash State:
  angle::LoadLA8ToRGBA8
  rx::Image11::loadData
  rx::TextureD3D::initializeContents
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552581:552589

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

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.

+Geoff, this is fixed by your CL right?

Very likely, yes.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot