Null-dereference WRITE in dawn_native::CommandAllocator::Allocate |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5750190964998144 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: 0x000000000000 Crash State: dawn_native::CommandAllocator::Allocate dawn_native::CommandBufferBuilder::PassEnded dawn_native::ProgrammablePassEncoder::EndPass Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=614680:614682 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5750190964998144 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 18
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/6f0e1f9d8235842e3c1130e4133e92e850166584 (Remove BufferView and inline offset/size in BindGroup). 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.
,
Dec 27
ClusterFuzz has detected this issue as fixed in range 619011:619012. Detailed report: https://clusterfuzz.com/testcase?key=5750190964998144 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: 0x000000000000 Crash State: dawn_native::CommandAllocator::Allocate dawn_native::CommandBufferBuilder::PassEnded dawn_native::ProgrammablePassEncoder::EndPass Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=614680:614682 Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=619011:619012 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5750190964998144 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.
,
Dec 27
ClusterFuzz testcase 5750190964998144 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 18Labels: ClusterFuzz-Auto-CC