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

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

This suddenly started crashing MSan builds on startup. Can you please take a look soon, this blocks fuzzing using MSan builds

ClusterFuzz has detected this issue as fixed in range 489186:489237.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  cc::LayerTreeHostImpl::SetContentHasNonAAPaint
  cc::LayerTreeHost::FinishCommitOnImplThread
  cc::ProxyImpl::ScheduledActionCommit
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=489104:489161
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=489186:489237

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


See https://github.com/google/clusterfuzz-tools 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 5705966707539968 is verified as fixed, so closing issue as verified.

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