New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 903234 link

Starred by 1 user
Status: Assigned
Owner:
lakshm...@chromium.org
Cc:
█ gmx@chromium.org
lakshm...@chromium.org
manojgupta@chromium.org
cmt...@chromium.org
█ chongjiang@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in chromeos_quipper_perf_reader_read_fuzzer

Project Member Reported by ClusterFuzz, Nov 8 
Detailed report: https://clusterfuzz.com/testcase?key=5075689960898560

Fuzzer: libFuzzer_chromeos_quipper_perf_reader_read_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  chromeos_quipper_perf_reader_read_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3110656:3111045

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

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
Project Member

Comment 1 by ClusterFuzz, Nov 8

Cc: lakshm...@chomium.org gmx@chromium.org chongjiang@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.

Comment 2 by manojgupta@chromium.org, Nov 8

Cc: cmt...@chromium.org

Comment 3 by manojgupta@chromium.org, Nov 8

Cc: lakshm...@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by manojgupta@chromium.org, Nov 12

Cc: -lakshm...@chomium.org
Owner: lakshm...@chromium.org
Project Member

Comment 5 by ClusterFuzz, Dec 1

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

Comment 6 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
Project Member

Comment 7 by ClusterFuzz, Dec 4

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

Comment 8 by metzman@google.com, Dec 4

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. 
The testcase is still reproducible. 
This was caused by another bug in ClusterFuzz that has been fixed. 
Sorry again for the inconvenience.
►

Sign in to add a comment