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/+/593cc44ba056aa6b278a73af08bc8bf814351512 (Let CredentialsContainer call mojom::CredentialManager directly.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 526173:526174.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e90000256f
Crash State:
  blink::CheckSecurityRequirementsBeforeRequest
  blink::CredentialsContainer::preventSilentAccess
  blink::V8CredentialsContainer::preventSilentAccessMethodCallback
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=525693:525709
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526173:526174

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

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

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

The issue was marked as verified before the fix actually landed (see  Issue 797900 ).