Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/3f4536894ac3001c53256d08d1e85aa442eb0f02 (d8: Make in process stack dumping optional).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Not the right owner... My CL just makes ASan stacktrace printing work again.

ClusterFuzz has detected this issue as fixed in range 50650:50651.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7fffbcb93fe0
Crash State:
  v8::internal::CheckObjectType
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=45141:45142
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=50650:50651

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

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

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