New issue
Advanced search Search tips

Issue 912299 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Indirect-leak in dawn_native::DeviceBase::CreateCommandBufferBuilder

Project Member Reported by ClusterFuzz, Dec 5

Issue description

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

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: Indirect-leak
Crash Address: 
Crash State:
  dawn_native::DeviceBase::CreateCommandBufferBuilder
  dawn_wire::server::Server::HandleDeviceCreateCommandBufferBuilder
  dawn_wire::server::Server::HandleCommands
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452

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

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 5

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 2 by ClusterFuzz, Dec 5

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

Comment 3 by ClusterFuzz, Dec 6

Labels: OS-Chrome
Components: Internals>GPU>Dawn
Project Member

Comment 5 by ClusterFuzz, Dec 8

ClusterFuzz has detected this issue as fixed in range 614747:614760.

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

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: Indirect-leak
Crash Address: 
Crash State:
  dawn_native::DeviceBase::CreateCommandBufferBuilder
  dawn_wire::server::Server::HandleDeviceCreateCommandBufferBuilder
  dawn_wire::server::Server::HandleCommands
  
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=614747:614760

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

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 8

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