New issue
Advanced search Search tips

Issue 797477 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

ASSERT: minML <= maxML

Project Member Reported by ClusterFuzz, Dec 23 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6137247647924224

Fuzzer: libFuzzer_icu_uregex_open_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  minML <= maxML
  icu_60::RegexCompile::handleCloseParen
  icu_60::RegexCompile::doParseActions
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=395614:395804

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: kkaluri@chromium.org
Components: Tools>Stability>libFuzzer
Labels: M-64
Owner: kcc@chromium.org
Status: Assigned (was: Untriaged)
Predator has provided 6 possible suspects

1. [libFuzzer] simplify FuzzerInterface.h by kcc
2. [libFuzzer] add exeprimental -rss_limit_mb flag to fight against OOMs by kcc
3. [libFuzzer] do the merge faster and a bit less precise by kcc
4. [LibFuzzer] by delcypher
5. [libfuzzer] Refactoring coverage state-management code. by aizatsky
6. [libFuzzer] enhance -rss_limit_mb and enable by default. Now it will print the OOM reproducer. by kcc

As per predator suspects, assigning it to the kcc@

kcc@ could you please look into it.

Comment 2 by mmoroz@chromium.org, Mar 29 2018

Owner: ----
Status: Untriaged (was: Assigned)
kcc@ is a developer of libFuzzer, but not of ICU where the bug lives in. Please assign this to ICU owner.
Labels: Test-Predator-Wrong-CLs M-69
Owner: js...@chromium.org
Status: Assigned (was: Untriaged)
Predator has provided Wrong CL's

Using code search for file "regexcmp.cpp" and assigning it to jshin@ for his work on suspect file.
Project Member

Comment 4 by ClusterFuzz, Dec 1

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

Comment 5 by ClusterFuzz, Dec 1

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6137247647924224 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: -Unreproducible Reproducible
Status: Assigned (was: WontFix)
Sorry for the confusion in c#4-c#5, this is still a valid issue.
Cc: pnangunoori@chromium.org js...@chromium.org
 Issue 910853  has been merged into this issue.

Sign in to add a comment