diff options
| -rw-r--r-- | docs/faq.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/faq.md b/docs/faq.md index 0a6b1b69..3c3212a8 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -34,8 +34,8 @@ to accept your project at this time! ## How timeouts and OOMs are handled? If a single input to a [fuzz target](glossary.md#fuzz-target) -requires more than **~25 seconds** or more than **2Gb RAM** to process we report this as a -timeout or an OOM (out-of-memory) bug +requires more than **~25 seconds** or more than **2GB RAM** to process, we +report this as a timeout or an OOM (out-of-memory) bug (examples: [timeouts](https://bugs.chromium.org/p/oss-fuzz/issues/list?can=1&q=%22Crash+Type%3A+Timeout%22), [OOMs](https://bugs.chromium.org/p/oss-fuzz/issues/list?can=1&q="Crash+Type%3A+Out-of-memory")). This may or may not be considered as a real bug by the project owners, @@ -43,7 +43,7 @@ but nevertheless we treat all timeouts and OOMs as bugs since they significantly reduce the efficiency of fuzzing. Remember that fuzzing is executed with AddressSanitizer or other -sanitizers which introduce certain ovehead in RAM and CPU. +sanitizers which introduce a certain overhead in RAM and CPU. We currently do not have a good way to deduplicate timeout or OOM bugs. So, at every point we report only one timeout and only one OOM bug per one fuzz target. |