Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/5e811aeee56483b64d66d2325fd37c14a55b600c (Add render pass color and depth stencil attachment descriptor).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Hi Corentin, could you take a look at this issue?

ClusterFuzz has detected this issue as fixed in range 619011:619012.

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

Fuzzer: afl_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000018
Crash State:
  dawn_wire::server::Server::OnMapWriteAsyncCallback
  dawn_native::null::Device::SubmitPendingOperations
  dawn_native::DeviceBase::Tick
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=617856:617868
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=619011:619012

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

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.

ClusterFuzz testcase 6303952278388736 is verified as fixed, so closing issue as verified.

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