csharrison, could you take a look and re-assign as appropriate?  Thanks.

ClusterFuzz has detected this issue as fixed in range 423366:423427.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5237069830160384

Fuzzer: libfuzzer_html_preload_scanner_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  AddValueForStrcmp
  findValueImpl
  blink::findValue
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=421508:421597
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=423366:423427

Minimized Testcase (0.24 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95NWyVYhXjMeHFPblh3wO1zw2x3uulL6Blp1vWW-6JfkdKDZp2FHIlMnvko6PXBtX03fgw0UezjYOci17HGSXmEFKDV_NEl8TUE9mqnhEhuu1uKJANfkS-i5LxifjvLV6AxLXHPb36Y7RV9y6P8Pg6lMeDwkA?testcase_id=5237069830160384

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

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

+tsepez, is there a way to get a tighter verified range for this fix? This morning, three outstanding clusterfuzz issues were "fixed" and I want to make sure the fix is real. I haven't had time to track down the root cause, and some of the issues seemed to be my own bugs setting up the libfuzzer tests.

Other bugs:
 issue 644273 
 issue 645683 

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