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

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

Automatically adding ccs based on suspected regression changelists:

Implement sRGB conversion in the blitter. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/1ab837c5764529c44666a6adaeddcaa5584b4356

Separate image depth and samples count. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/bfa23b3f4de49586d2bd25efb77fa92734bd6f26

Use half-precision for special internal formats. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/a6bc61d61d6fe9551d72f917629bf6bccfeafce0

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Same as previous graphicsfuzz issue. Marking as duplicate.

Could you add capn@chromium.org to CC in Issue 912602 ? Thanks.

ClusterFuzz has detected this issue as fixed in range 624262:624279.

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

Fuzzer: metzman_graphicsfuzz_crash_fuzzer
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7fb4ad1b4adf
Crash State:
  sw::Thread::Thread
  sw::Renderer::initializeThreads
  sw::Renderer::updateConfiguration
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=529109:529110
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=624262:624279

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.