[llvm-bugs] Issue 4815 in oss-fuzz: llvm/clang-fuzzer: Timeout in llvm_clang-fuzzer

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Wed Dec 27 16:21:25 PST 2017

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.com, llvm-b... at lists.llvm.org, v... at apple.com,  
akils... at apple.com
Labels: ClusterFuzz Unreproducible Engine-libfuzzer Proj-llvm  
Type: Bug

New issue 4815 by ClusterFuzz-External: llvm/clang-fuzzer: Timeout in  

Detailed report: https://oss-fuzz.com/testcase?key=5330748035825664

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address:
Crash State:

Sanitizer: address (ASAN)

Reproducer Testcase:  

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

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.

When you fix this bug, please
   * mention the fix revision(s).
   * state whether the bug was a short-lived regression or an old bug in any  
stable releases.
   * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  

You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171227/620bfe98/attachment.html>

More information about the llvm-bugs mailing list