New issue
Advanced search Search tips

Issue 915449 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 29
Cc:
cwallez@chromium.org
kainino@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in dawn_native::CommandAllocator::GetNewBlock

Project Member Reported by ClusterFuzz, Dec 15 
Detailed report: https://clusterfuzz.com/testcase?key=4508916039548928

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: chromeos_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  dawn_native::CommandAllocator::GetNewBlock
  dawn_native::CommandAllocator::Allocate
  dawn_native::CommandBufferBuilder::BeginComputePass
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=chromeos_libfuzzer_chrome_asan&range=614751:614765

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
Project Member

Comment 1 by ClusterFuzz, Dec 15

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 15

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 4508916039548928 appears to be flaky, updating reproducibility label.
Project Member

Comment 3 by ClusterFuzz, Dec 29

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 4508916039548928 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment