New issue
Advanced search Search tips

Issue 906440 link

Starred by 1 user
Status: Assigned
Owner:
skau@chromium.org
Cc:
briannorris@chromium.org
pawliczek@chromium.org
luum@chromium.org
skau@chromium.org
metzman@chromium.org
manojgupta@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

ghostscript fuzzer: libFuzzer: timeout after 25 seconds

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

Fuzzer: libFuzzer_chromeos_gstoraster_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  NULL
Sanitizer: address (ASAN)

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

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

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 18

Cc: pawliczek@chromium.org briannorris@chromium.org luum@chromium.org skau@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 briannorris@chromium.org, Nov 19

Components: Internals>Printing>CUPS

Comment 3 by briannorris@chromium.org, Nov 19

Summary: ghostscript fuzzer: libFuzzer: timeout after 25 seconds

Comment 4 by manojgupta@chromium.org, Nov 28

Owner: skau@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5675834557595648 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 5675834557595648 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