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

Issue 903772 link

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



Sign in to add a comment

Abrt in /usr/lib64/libc++abi.so.1

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

Fuzzer: libFuzzer_chromeos_quipper_perf_reader_read_fuzzer
Job Type: libfuzzer_ubsan_chromeos
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x000000000001
Crash State:
  /usr/lib64/libc++abi.so.1
  /usr/lib64/libc++abi.so.1
  /usr/lib64/libc++abi.so.1
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_ubsan_chromeos&range=3110653:3111064

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

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 9

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 12

Cc: -lakshm...@chomium.org lakshm...@chromium.org
Owner: lakshm...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 3 by ClusterFuzz, Dec 1

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

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

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

Comment 6 by metzman@chromium.org, Dec 4

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

Comment 7 by manojgupta@google.com, Jan 18 (4 days ago)

Cc: -manojgupta@google.com manojgupta@chromium.org
►

Sign in to add a comment