Oh damn, the fuzzer is starting to abuse assertPromiseResult, resulting in AbortJS being called...

Including Andreas and Mathias who wanted to refactor this anyway. Maybe now is the time?

Yeah, I have seen the fuzzer finding the eval("%FooBar()") pattern before and hence side-stepping the fuzzer white-list of allowed runtime functions. This has happened even before assertPromiseResult a couple of times. But wasn't annoying enough yet for anyone to take action. :/

I have it on my list, I will do it latest at the next Cleanup Friday.

ClusterFuzz has detected this issue as fixed in range 53203:53204.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x55c945585a42
Crash State:
  NULL
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=48565:48566
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=53203:53204

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

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

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