Predator and CL could not provide any possible suspects.
Using the code search for the file, “verify_name_match_normalizename_fuzzer.cc” assigning to concern owner from GIT revision log.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/7b45a27c473f13756026dd4d066bb42529c694cb

@eroman -- Could you please look into this issue as you have worked on the suspect file recently, kindly reassign if it has nothing to do with your changes.

Thank You.

same as  issue 789802 , but dunno if clusterfuzz bugs should be duped?

ClusterFuzz has detected this issue as fixed in range 521033:521072.

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

Fuzzer: libFuzzer_net_cert_normalize_name_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900005ceb
Crash State:
  verify_name_match_normalizename_fuzzer.cc
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=520172:520207
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=521033:521072

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5716153770180608 is verified as fixed, so closing issue as verified.

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