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

Issue 822588 link

Starred by 1 user
Status: Verified
Owner:
█ junyer@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
█ brajkumar@chromium.org
kcc@chromium.org
mmoroz@chromium.org
metzman@chromium.org
mbarbe...@chromium.org
infe...@chromium.org
och...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug

Blocked on:
issue 828032


Sign in to add a comment

Out-of-memory in third_party_re2_fuzzer

Project Member Reported by ClusterFuzz, Mar 16 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5490592625459200

Fuzzer: libFuzzer_third_party_re2_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  third_party_re2_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=508794:508826

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Mar 20 2018

Cc: brajkumar@chromium.org
Components: Blink
Labels: -Pri-1 M-66 Test-Predator-Wrong Pri-2
Owner: junyer@chromium.org
Status: Assigned (was: Untriaged)
> From the provided CL under regression range, observing multiple changes related to re2, so unable to pinpoint the exact suspect CL. 
CL: https://chromium.googlesource.com/chromium/src/+/19d4ff3a9ad5c20228bfb602c6b7b44086852afc

> By comparing the stack trace this issue looks similar to  bug 790735 , hence assigning to @junyer for more updates on this issue.

Thanks!

Comment 3 by junyer@google.com, Mar 20 2018 

Note that there have been zero pertinent changes to RE2 – the only thing that changed a few days ago was the README file! ASan memory footprint seems to be the culprit?

Comment 4 by dtapu...@chromium.org, Mar 20 2018

Components: -Blink Tools>Stability>libFuzzer
Live Heap Allocations is only 108979368 bytes yet the 2gb limit for libfuzzer was reached.

Comment 5 by mmoroz@chromium.org, Apr 9 2018

Blockedon: 828032
Project Member

Comment 6 by ClusterFuzz, Apr 12 2018

Labels: OS-Mac
Project Member

Comment 7 by ClusterFuzz, Apr 12 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5490592625459200 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment