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/+/0298df882b39e2f2d2e2a5d41917d515accc36e8 ([turbofan] Add feedback to CheckSmi).

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

jkummerow@ showed me that this issue can be reproduced on linux with the build options from clusterfuzz and after setting ASAN_OPTIONS and stack limit accordingly:

$ export ASAN_OPTIONS="redzone=128:external_symbolizer_path="`pwd`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer":symbolize=1:handle_sigill=1:handle_segv=1:use_sigaltstack=1:strict_memcmp=0:allow_user_segv_handler=0:coverage=0:fast_unwind_on_fatal=1:handle_sigfpe=1:handle_sigbus=1:detect_stack_use_after_return=0:alloc_dealloc_mismatch=0:detect_leaks=0:print_scariness=1:allocator_may_return_null=1:handle_abort=1:check_malloc_usable_size=0:detect_container_overflow=0:quarantine_size_mb=100:detect_odr_violation=0:malloc_context_size=128:print_summary=1"

$ ulimit -s 1014

$ out.gn/x86.release.asan/d8  --random-seed=-1665162253 --invoke-weak-callbacks clusterfuzz.js  

Investigating.

ClusterFuzz testcase 6692448675037184 appears to be flaky, updating reproducibility label.