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

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

can't reproduce this on an ASan build and the crash itself looks strange. WontFixing.

ClusterFuzz has detected this issue as fixed in range 483471:483525.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x3092232F
Crash State:
  (unknown)
  (unknown)
  (unknown)
  
Memory Tool: SYZYASAN

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=465806:465843
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=483471:483525

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


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.

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