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/+/626c99e870b04e474408a5b35e97f260b9d787ba (Convert Cache Storage IPC to Mojo.).

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.

I'm already working on this issue on the other bug.

CL below is out for review to fix this issue:
https://chromium-review.googlesource.com/c/chromium/src/+/1011467

ClusterFuzz has detected this issue as fixed in range 551260:551263.

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x06e733b21958
Crash State:
  blink::CrossThreadPersistentRegion::ShouldTracePersistentNode
  blink::PersistentRegion::TracePersistentNodes
  blink::ThreadState::VisitPersistents
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=544931:544932
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551260:551263

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

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