Direct-leak in dawn_native::null::CreateDevice |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5973237764456448 Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: dawn_native::null::CreateDevice DawnWireServerAndFrontendFuzzer.cpp dawn_native::DeviceBase::DeviceBase Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5973237764456448 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 13
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/45ee4c88c43f2cd986a4af84ac4a8361a222b185 (Add a fuzzer for the wire server and Dawn frontend). 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.
,
Nov 19
,
Nov 20
The following revision refers to this bug: https://dawn.googlesource.com/dawn/+/c1bb72c5d299716bf2fe608b671b66b0570a7192 commit c1bb72c5d299716bf2fe608b671b66b0570a7192 Author: Corentin Wallez <cwallez@chromium.org> Date: Tue Nov 20 09:14:40 2018 DawnWireAndFrontendFuzzer: don't leak the device. The dawn::Device(dawnDevice) constructor was adding a reference which caused the device to leak. Fix this by using dawn::Device::Acquire instead. BUG= chromium:904734 Change-Id: Id641459f9285c9da51a0d2a1f88126197bfd79a5 Reviewed-on: https://dawn-review.googlesource.com/c/2561 Reviewed-by: Dan Sinclair <dsinclair@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> [modify] https://crrev.com/c1bb72c5d299716bf2fe608b671b66b0570a7192/src/fuzzers/DawnWireServerAndFrontendFuzzer.cpp
,
Nov 21
ClusterFuzz has detected this issue as fixed in range 609745:609751. Detailed report: https://clusterfuzz.com/testcase?key=5973237764456448 Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: dawn_native::null::CreateDevice DawnWireServerAndFrontendFuzzer.cpp dawn_native::DeviceBase::DeviceBase Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=609745:609751 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5973237764456448 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.
,
Nov 21
ClusterFuzz testcase 5973237764456448 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
, Nov 13Labels: ClusterFuzz-Auto-CC