Timeout in sqlite3_prepare_v2_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5204267400167424 Fuzzer: libFuzzer_sqlite3_prepare_v2_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: sqlite3_prepare_v2_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5204267400167424 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. If the fix resolved the issue, please close the bug by marking as Fixed. Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 11 2017
,
Sep 12 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "sqlite3_prepare_v2_fuzzer" assigning to the related owner. @mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Sep 12 2017
Interesting, we don't have that issue on OSS-Fuzz. I think we should roll sqlite3 and then use the updated fuzz target.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid. (bulk edit)
,
Nov 7 2017
,
Jan 18 2018
,
Feb 23 2018
ClusterFuzz testcase 5204267400167424 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by manoranj...@chromium.org
, Aug 17 2017