Null-dereference READ in HandleDynamicTypeCacheMiss |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6090796685852672 Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer Fuzz target binary: dawn_wire_server_and_frontend_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x00000000001c Crash State: HandleDynamicTypeCacheMiss dawn_wire::server::ForwardBufferMapWriteAsync dawn_native::BufferBase::~BufferBase Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=615329:615346 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6090796685852672 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 14
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/a49242766a107c411d744d828a733317ef92dc83 (Render Pipeline Descriptorization -- Part I). 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 14
,
Dec 15
ClusterFuzz has detected this issue as fixed in range 616973:616974. Detailed report: https://clusterfuzz.com/testcase?key=6090796685852672 Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer Fuzz target binary: dawn_wire_server_and_frontend_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x00000000001c Crash State: HandleDynamicTypeCacheMiss dawn_wire::server::ForwardBufferMapWriteAsync dawn_native::BufferBase::~BufferBase Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=615329:615346 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=616973:616974 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6090796685852672 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 15
ClusterFuzz testcase 6090796685852672 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 14Labels: ClusterFuzz-Auto-CC