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

This seems similar to 758139. tzik@, could you take a look?

ClusterFuzz has detected this issue as fixed in range 497582:497621.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x07533940
Crash State:
  v8::debug::ConsoleDelegate::`vcall'{56}'
  base::internal::ReturnAsParamAdapter<long
  base::internal::FunctorTraits<void
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=493893:493928
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=497582:497621

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

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

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

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