// Not sure how we'd suppress that. Function with lazy-error in eval is added in lazy and not in eager:

try {
  eval("function Crash() { assertUnreachable(); continue;if (Crash) {  } }");
} catch(e) {; }
print(Object.getOwnPropertyNames(this).length)

// Afterwards fuzz tests might do whatever with the global object's properties which differ :/

ClusterFuzz has detected this issue as fixed in range 44902:44903.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_eager
  sources: 89e
  
Sanitizer: address (ASAN)

Regressed: V8: 43144:43145
Fixed: V8: 44902:44903

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


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

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

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.