Bisects to Michis CL which enables the native heap for wasm by default (afd8a81884b51f95595d9977723cb8bcb8f31c6b).

Anyway, the stack trace looks like there is another problem here (some intermediate methods removed):

#0 base::OS::Abort
#1 CancelableTaskManager::Register
#5 ConcurrentMarking::ScheduleTasks
#6 IncrementalMarking::StartMarking
#9 Space::AllocationStep
#11 SpaceWithLinearArea::RemoveAllocationObserver
#14 Isolate::TearDown

So assigning to Ulan, to check whether it's intended that during Isolate::TearDown, a new task for concurrent marking is created.

ClusterFuzz has detected this issue as fixed in range 50640:50641.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !canceled_ in cancelable-task.cc
  v8::internal::CancelableTaskManager::Register
  v8::internal::Cancelable::Cancelable
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=50497:50498
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=50640:50641

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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