This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

In the regression range provided, there were no changes to the code being fuzzed. Suspecting this is caused by the libfuzzer roll.

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

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

Fuzzer: libfuzzer_stylesheet_contents_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  AddValueForMemcmp
  equal<unsigned
  equalInternal<unsigned
  
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.39 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97WlCUvcP8UxRtlJ-SfvJksppn92LBIbgK4eUGvs7w_mhENAJUinzHObRpNagxYHVJbToRQFGTGfYjnRwo4xEXUbs4IwzTL0fEbBHDtTU6-QPZWOqyDEmU9sV_WkePjFayuWrX0LvfPzotWO0hopbc_dyoJuA?testcase_id=6147485456400384

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.