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

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

ClusterFuzz has detected this issue as fixed in range 521927:521929.

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

Job Type: linux_asan_chrome_mp
Crash Type: CHECK failure
Crash Address: 
Crash State:
  untyped_->count(reinterpret_cast<Address>(slot)) > 0 in heap.cc
  v8::internal::SlotVerifyingVisitor::VisitPointers
  void v8::internal::BodyDescriptorApply<v8::internal::CallIterateBody, void, v8::
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=477280:477303
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=521927:521929

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

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

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