Predator and CL did not find any possible suspects.
Using Code Search for the file, "template_url_data.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/8b5fc83dba9f525b0f707433a9fbb91465ca9bdd

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

ClusterFuzz has detected this issue as fixed in range 463054:463440.

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

Fuzzer: libfuzzer_template_url_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !short_name.empty() in template_url_data.cc
  TemplateURLData::SetShortName
  TemplateURLParsingContext::EndElementImpl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=463017:463054
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=463054:463440

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97OA5Ci9kpnUu-uUEWD1wk-04cpCP9RP2DbHzxTqXFXRZAMagkMJA9iFDPsao9nL10mQVyML2gV9lJC-bp9EFDOJVG-1xg9c-mJr0WevsSg8FNOfFdrS9fne98cUFx-Pq34W8gwsD-YMcey-1B2SWMZetzVC0dAPzrZMm6_4RGdXgik9UDUbjvf2f5wbpgYmBcxV88R1K2FoK1Pn3WDfpCIGpGHuIA0vHQd8E6Robm6-jeZNtAysbNFoBipmvOvpy9g063GXQ6CGCrR6rDLDbt_LzWe25ziv1kKkC2918g0YJ0jcSBQaMJp81cxqY87ioHKyAUK3dAvbE_vcmQ_hMQfLwXpryPdO_K04KHHVivIDlEICHI?testcase_id=6538631465664512


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

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

Has this issue been fixed already. And it looks that regression list does not contain any of my change and I am not the owner of template_url_data.cc and not quite familiar with that part. And I am not sure how is the owner of it. If not fixed, maybe need someone help with a reassignment.

@pkasting: this looks the same as  bug 714081 ? Any idea the reason for it or who could help with it?