Hang in sqlite3_ossfuzz_fuzzer |
||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4538574604337152 Fuzzer: libfuzzer_sqlite3_ossfuzz_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Hang Crash Address: Crash State: sqlite3_ossfuzz_fuzzer Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=433935:434071 Minimized Testcase (0.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96s7ilv374EtGT3-62Y1Kh6ko-nPKWima1bDKmgeXcx5fM_joKIRKIwMmOWoKM0fb5Oela5fzcVmCBf7z7Cj4_MeidKLdEi61oYtRRo2f7_NvLKG7BXll_2J_Zb5Q0ekSqq3XcreWsA2z6RaxYRjzxLwvVDXA?testcase_id=4538574604337152 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Dec 1 2016
Unable to find the possible suspect using Find it. Assigning to the concern owner from the regression range -- https://chromium.googlesource.com/chromium/src/+log/f0126ea00c414108b3043b93e2270beefb27cc4b..d78075be67a3ee6520d1f8377cd69b478ebdf5ee?pretty=fuller Suspecting the below commit -- https://chromium.googlesource.com/chromium/src/+/656b55356751d12fd8c643f927691275ef10dded @mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Dec 1 2016
Passing it over to shess@ as an OWNER of sqlite3.
,
Dec 1 2016
,
Mar 16 2017
,
Mar 21 2017
ClusterFuzz has detected this issue as fixed in range 458147:458197. Detailed report: https://clusterfuzz.com/testcase?key=4538574604337152 Fuzzer: libfuzzer_sqlite3_ossfuzz_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: sqlite3_ossfuzz_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=433935:434071 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=458147:458197 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97X_C4bmqNE_uENOrlM71FTjQ-oG3flQsTCATOwE9S6kh-x_yFTFiBdjEKZAMkLSqNYdjxArV4ma5AMTyOnlp4crAizRjxZgpe5GVVj2TLPeBR6LZLCwFiOPfT86JZWHzIbaoyD7f8c2BMUikWfStQJ3OFazxdTJwMn0EseqHYk4XTFDHWY4hkeUPU13UoCswUK5z1q65U0NFKO-RgFDYMtSTnrgi03oKMKH77YspR9zLQxZlMa1YZB4rZEjjJJ_fUiZj0AFyRShZpT3hpE8U37VsDGf8NNmNemf5Bst7NaCyjJhkohYwBTvVv1Iv6x7LLVHdkwZ9tm4Tl2Y6OIn7JLCiqL_LKpA4hj9cdILq8xLUTWNqw?testcase_id=4538574604337152 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Mar 21 2017
ClusterFuzz testcase 4538574604337152 is verified as fixed, 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 ajha@chromium.org
, Nov 24 2016