google / google/oss-fuzz

Reproducible crashes marked as non-reproducible?

Open
#13,495 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
12.6k
Forks
2.9k
Avg merge
2d 2h
Merged PRs (30d)
62

Description

I'm seeing the second "non-reproducible" crash in the last couple of weeks which turned out to be reproducible: https://oss-fuzz.com/testcase-detail/5227577549848576. Both issues were caused by assertion failures aborting the fuzzer and not by sanitizers. I also can't see any obvious source of non-determinism but maybe I'm missing something.

Contributor guide

Open the contributing guide

Research direction

Start with the linked OSS-Fuzz testcase 5227577549848576 and investigate how assertion-failure crashes are classified as non-reproducible. Compare that path with sanitizer-triggered crashes; done means reproducible assertion crashes are classified consistently.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.