capn@: Looks like you landed a swiftshader-related change in the regression range: https://codereview.chromium.org/2814073004

I don't know if this is actually related, but could you help triage this security bug?

ClusterFuzz has detected this issue as fixed in range 477971:477993.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x0e987000
Crash State:
  sw::Renderer::taskLoop
  sw::Renderer::threadLoop
  sw::Renderer::threadFunction
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=464127:464479
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=477971:477993

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5208574841323520 is verified as fixed, so closing issue.

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

The SwiftShader test that was added in the regression range wouldn't have caused this. It's a crash within dynamically generated code, but there's not much to go on to determine a more precise cause. My best guess is an unclean shutdown (note the DbgHelp error) due to another crash, and that got fixed recently (possibly https://chromium-review.googlesource.com/528098).

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