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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_v8_mipsel_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  isolate_status.count(args.GetIsolate()) == 1 in d8.cc
  v8::Shell::NotifyDone
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: address (ASAN)

Regressed: V8: 45164:45165

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

ClusterFuzz has detected this issue as fixed in range 45176:45177.

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  isolate_status.count(args.GetIsolate()) == 1 in d8.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 45164:45165
Fixed: V8: 45176:45177

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


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 has detected this issue as fixed in range 45176:45177.

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_v8_mipsel_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  isolate_status.count(args.GetIsolate()) == 1 in d8.cc
  v8::Shell::NotifyDone
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: address (ASAN)

Regressed: V8: 45164:45165
Fixed: V8: 45176:45177

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


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

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