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

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

clemensh: Can you help route? Clusterfuzz didn't find a regression range for this.

Thanks, I am the right owner for this, as I fixed a very similar (maybe the same) issue in https://crrev.com/c/1051235. Will have a look on Monday.

This is not a security bug though, as it requires the --code-comments command line flag.

ClusterFuzz has detected this issue as fixed in range 53099:53100.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x561d49c5a0a8
Crash State:
  Bad-cast to v8::internal::compiler::Operator1<v8::internal::ExternalReference, v8::internal::compiler::OpEqualTo<v8::internal::ExternalReference>, v8::internal::compiler::OpHash<v8::internal::ExternalReference> > from v8::internal::compiler::CommentOperator
  OpParameter<v8::internal::ExternalReference>
  v8::internal::compiler::OperandGenerator::ToConstant
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=53099:53100

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

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

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