Predator and CL could not provide any possible suspects.
Using Code Search for the file, "CredentialsContainer.cpp" assigning to the concern owner who might be related.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/593cc44ba056aa6b278a73af08bc8bf814351512

engedy@-- Could you please look into the issue, kindly re-assign if this is not related to your changes.


Thank You.

Who would be the right point of contact to discuss other potential error conditions that might result in this stack trace?

I am quite puzzled by this as I don't think the fuzzer exercises the credential management API at all.

ClusterFuzz has detected this issue as fixed in range 526962:526965.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Security CHECK failure
Crash Address: 
Crash State:
  resolver->GetFrame() in CredentialsContainer.cpp
  blink::CheckSecurityRequirementsBeforeRequest
  blink::CredentialsContainer::create
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=526173:526175
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=526962:526965

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

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.