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

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

Could be regression from https://chromium-review.googlesource.com/c/chromium/src/+/903942 based on regression range.

ClusterFuzz has detected this issue as fixed in range 535922:535929.

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

Fuzzer: j00ru_htmlcss_fuzz
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x2a891fdb3bb8
Crash State:
  Bad-cast to blink::GarbageCollectedMixinblink::ObjectAliveTrait<blink::ActiveScriptWrappableBase, true>::IsHeapObjectAlive
  bool WTF::TraceInCollectionTrait<
  blink::ThreadHeap::WeakProcessing
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=535301:535306
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=535922:535929

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

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.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot