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

Issue 907912 link

Starred by 1 user
Status: Assigned
Owner:
js...@chromium.org
Cc:
█ sh...@chromium.org
mpdenton@chromium.org
pwnall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

ASSERT: restoreInputLen >= fActiveLimit

Project Member Reported by ClusterFuzz, Nov 22 
Detailed report: https://clusterfuzz.com/testcase?key=6352671214403584

Fuzzer: libFuzzer_sqlite3_ossfuzz_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  restoreInputLen >= fActiveLimit
  icu_63::RegexMatcher::MatchChunkAt
  icu_63::RegexMatcher::matches
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=608964:608970

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6352671214403584

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Nov 22

Cc: sh...@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Nov 22

Labels: Test-Predator-Auto-Owner
Owner: mpdenton@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/5cb3a6cd8648c1585a8bd47c8333c5e406476527 (Fixed sqlite fuzzer to use upstream version).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 3 by mpdenton@google.com, Nov 26

Cc: js...@chromium.org mpdenton@chromium.org
Components: Internals>Storage
Owner: pwnall@chromium.org
Also adding maintainer of icu in case the bug is not in the sqlite code.

Comment 4 by pwnall@chromium.org, Nov 26

Labels: ClusterFuzz-Wrong
Added ClusterFuzz-Wrong because of Comment 1 -- shess@ is no longer working on Chromium, and I now handle the bugs in //third_party/sqlite.

mpdenton@: Any chance the ClusterFuzz heuristics could be improved, so you don't have to manually route these bugs? :D I suspect there's a bug or stale cache involved -- shess@ is no longer listed in OWNERS, and I show up quite often in the last year's commit history.
Project Member

Comment 5 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6352671214403584 appears to be flaky, updating reproducibility label.

Comment 6 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

Comment 7 by pwnall@chromium.org, Jan 13

Cc: -js...@chromium.org pwnall@chromium.org
Owner: js...@chromium.org
I think this is in ICU. Removing myself from this, as I'm focusing on the flurry of real SQLite clusterfuzz issues.
►

Sign in to add a comment