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/+/413675e9b667e07ae84a115268abedfdb7430740 (Run PrioritizedTaskRunner tasks with the same priority in posting order).

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.

ClusterFuzz has detected this issue as fixed in range 565095:565096.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  void net::PrioritizedTaskRunner::PostTaskAndReplyWithResult<int, int>
  disk_cache::SimpleEntryImpl::DoomEntryInternal
  disk_cache::SimpleEntryImpl::RunNextOperationIfNeeded
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=564929:564933
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=565095:565096

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

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

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

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