New issue
Advanced search Search tips

Issue 911112 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
kerrnel@chromium.org
metzman@chromium.org
manojgupta@chromium.org
xiaochu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in imageloader::HelperProcessReceiver::OnFileCanReadWithoutBlocking

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

Fuzzer: libFuzzer_chromeos_imageloader_helper_process_receiver_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x000000000001
Crash State:
  imageloader::HelperProcessReceiver::OnFileCanReadWithoutBlocking
  imageloader::helper_process_receiver_fuzzer_run
  helper_process_receiver_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3138110:3138341

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

Issue manually filed by: mmoroz

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

Comment 1 by ClusterFuzz, Dec 3

Cc: kerrnel@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 4

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

Comment 3 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 a bug in ClusterFuzz that has been fixed. 
Sorry for the inconvenience.

Comment 4 by manojgupta@chromium.org, Dec 5

Cc: xiaochu@chromium.org
Is this dupe of  bug 906352 ?

Comment 5 by xiaochu@chromium.org, Dec 5 

yes, Abrt is caused by the same LOG(FATAL).
►

Sign in to add a comment