Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Assigning to capn@ based on suspected regression CLs (clusterfuzz wasn't very precise but they were all attributed to capn@).

ClusterFuzz has detected this issue as fixed in range 546924:546952.

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  sw::Surface::Buffer::write
  sw::Surface::Buffer::write
  sw::Surface::copyInternal
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=529740:529750
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=546924:546952

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

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

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

Was also fixed by https://swiftshader-review.googlesource.com/18128

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