This is properly reporting an OOM situation via {i::V8::FatalProcessOutOfMemory} which will invoke any Chrome provided {FatalErrorCallback} when compiled into Chrome. For a standalone (i.e. "d8") build, we report it to the console as a safe crash with the message "Allocation failed - JavaScript heap out of memory". In short, this is working as intended.

I will keep this issue open on the triaging list for V8 ClusterFuzz issues as a place-holder for ClusterFuzz reports to be merged into. There is nothing actionable here.

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=5813335567630336

Fuzzer: mbarbella_js_mutation
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Fatal error
Crash Address: 
Crash State:
  MarkCompactCollector:
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_d8&range=386994:387080

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96su2PBDM3nszHDghyxUwdZusg795j88LczmJgTvC_FNJOhJoxo2xjaz5dKbn6xu-MrksoCeJfpJMuJn9eGpZLMtoPhpgbotxy2jmfA1beabqU9UPS_UsL8Ug_bCoxU6xjDlGk-XJuw1l-Rifacocigoo21TA


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

As per Comment# 5, ClusterFuzz has detected the test case as potentially fixed, so changing the status to Fixed.
Please undo if that is not the case.
Thank You.