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/chromium/src/+/adc4f1e5aa8b792e2a9a4fb359a7d4e0855c3e77 ([cleanup] Remove a bunch of stable houdini api flags.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

My patch didn't have any behavior change, and just removed a bunch of stable flags that have already been shipped.

ClusterFuzz has detected this issue as fixed in range 569185:569186.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !scope.AccessCheckFailed() in v8_dom_wrapper.cc
  blink::V8DOMWrapper::CreateWrapper
  blink::ScriptWrappable::Wrap
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=563877:563878
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=569185:569186

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

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

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