As discussed offline. This seems to be a new (properly reported) OOM that starts happening since the "improved diagnostics". Not sure whether this is relevant and actionable to you guys. Feel free to close if it's not. Also let me know if you need help to repro, I can help.

https://chromium.googlesource.com/v8/v8/+/1ef7487b657e4b1a86cf778ac062b25de5001af7

Working as intended: out of memory. https://codereview.chromium.org/1873443002 changed the OOM error message slightly.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6580152334548992

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_ignition_dbg
Platform Id: linux

Crash Type: Fatal error
Crash Address: 
Crash State:
  invalid
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_d8_ignition_dbg&range=35430:35431

Minimized Testcase (8.29 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96WnaEKbXEOhK4TtoqPBBuetsjs-UzBcWp63T3YkrTkJ5A1ie5gaNkHUGa1xAHezEGFdUmrZ_On8Nz36BWs4tjQhiS7trZVXrcMmGevAghchNzuLuvJ_zZtEu1uO-yoN8ug1bUneJ1j3Uph3QI8KtFffXdWhA?testcase_id=6580152334548992

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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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