capn, could you please take a look?

Alexis, this looks like a crash in generated code to me, which might be similar to the one you're looking into?

Despite crashing in Stable, I don't think this is P1, due to only affecting the GPU process.

This crash is caused by trying to allocate a 8192x8192x4 D32F texture, for a total of 1GB of memory for that single texture, which is really hard to allocate in a 32b executable with only 4GB of memory space.

Since this is simply an out of memory error, the crash is most likely the correct behavior in this case, so marking as WontFix.

ClusterFuzz testcase 6063280958472192 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 510178:510349.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Unknown exception
Crash Address: 0x0584d2b0
Crash State:
  Register
  libGLESv2_swiftshader
  libGLESv2_swiftshader
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=480776:480854
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=510178:510349

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

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.

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