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

Not sure if this is real or if it's an issue with the builds we're using. Will take a closer look tomorrow.

ClusterFuzz has detected this issue as fixed in range 477433:477527.

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

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  libglib-2.0.so.0
  g_main_context_new
  g_main_context_default
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=476541:476588
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=477433:477527

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


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

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

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