New issue
Advanced search Search tips

Issue 912476 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in dawn_native::null::Device::CreateBufferImpl

Project Member Reported by ClusterFuzz, Dec 6

Issue description

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

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: 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::Device::CreateBufferImpl
  dawn_native::DeviceBase::CreateBufferInternal
  dawn_native::DeviceBase::CreateBuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613934:613941

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Dec 6

Labels: OS-Chrome
Project Member

Comment 2 by ClusterFuzz, Dec 6

Cc: kainino@chromium.org cwallez@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

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

Comment 3 by ClusterFuzz, Dec 6

Labels: Test-Predator-Auto-Owner
Owner: cwallez@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/6f9d21e805424c82c3e41c0b8758ae7771f69bfd (Descriptorize BindGroups.).

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.
Components: Internals>GPU>Dawn
Project Member

Comment 5 by ClusterFuzz, Dec 7

ClusterFuzz has detected this issue as fixed in range 614680:614682.

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

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: 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::Device::CreateBufferImpl
  dawn_native::DeviceBase::CreateBufferInternal
  dawn_native::DeviceBase::CreateBuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613934:613941
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=614680:614682

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

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.
Project Member

Comment 6 by ClusterFuzz, Dec 7

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5285938680561664 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