New issue
Advanced search Search tips

Issue 922304 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

gstoraster_fuzzer: segfault

Project Member Reported by ClusterFuzz, Jan 16

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5168845568081920

Project: chromeos
Fuzzer: libFuzzer_chromeos_gstoraster_fuzzer
Fuzz target binary: gstoraster_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Null-dereference
Crash Address: 0x000000000018
Crash State:
  NULL
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for instructions to reproduce this bug locally.

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Jan 16

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.
Components: Internals>Printing>CUPS
Summary: gstoraster_fuzzer: segfault
I don't know what's up with these useless titles...
Brian, sorry about the titles I will look into it. 

Sign in to add a comment