New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666748 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in sqlite3_prepare_v2_fuzzer

Project Member Reported by ClusterFuzz, Nov 18 2016

Issue description

Comment 1 by ajha@chromium.org, Nov 21 2016

Labels: M-55
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by mmoroz@chromium.org, Dec 30 2016

Cc: kcc@chromium.org aizatsky@chromium.org
Owner: mmoroz@chromium.org
Another OOM with MSan build. Let's ignore it for now.
Project Member

Comment 4 by ClusterFuzz, Jan 12 2017

ClusterFuzz has detected this issue as fixed in range 442746:442796.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6136375721328640

Fuzzer: libfuzzer_sqlite3_prepare_v2_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  sqlite3_prepare_v2_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=395689:395794
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=442746:442796

Minimized Testcase (0.40 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94RtgcSWnnPsYNWR09tmaaFpPS98qk4Uger_w7cDxYC94V7mt8AltxB2Ruvuu6phd1RnBZsdIJ4koFsHrj4E-ukZWI9wuhFJZP1zi6QQLuRQsxDMKT6BG2bfrBVftbmhZiH0umEUISJx0U2A-lwdvXStWOx_Q?testcase_id=6136375721328640

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.
Project Member

Comment 5 by ClusterFuzz, Jan 12 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6136375721328640 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