Predator and CL did not provide any possible suspects.
Using code Search for the file, "v8_platform.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/4844f72ece1a4a870e571e8e53746bd4c7d3f6f6

@jochen -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Issue 721754 has been merged into this issue.

 Issue 719132  has been merged into this issue.

ClusterFuzz testcase 6173920935018496 is flaky and no longer reproduces, so closing issue.

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

ClusterFuzz testcase 5367250713575424 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 475250:475393.

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

Fuzzer: inferno_twister
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  gin::V8Platform::CallOnForegroundThread
  AsyncCompileJob::ExecuteCompilationUnits::Run
  base::WorkerThread::ThreadMain
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=475250:475393

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


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.