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

Issue 790735 link

Starred by 1 user
Status: Fixed
Owner:
█ junyer@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
pnangunoori@chromium.org
mmoroz@chromium.org
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in third_party_re2_fuzzer

Project Member Reported by ClusterFuzz, Nov 30 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5952362375282688

Fuzzer: libFuzzer_third_party_re2_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  third_party_re2_fuzzer
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.

Comment 1 by pnangunoori@chromium.org, Dec 1 2017

Cc: msrchandra@chromium.org mmoroz@chromium.org pnangunoori@chromium.org
Labels: Test-Predator-Wrong
Owner: junyer@chromium.org
Status: Assigned (was: Untriaged)
As per the   Issue 773953  owner, assigning this issue to @junyer.
@junyer -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.
Project Member

Comment 2 by ClusterFuzz, Dec 4 2017

Labels: OS-Mac

Comment 3 by junyer@google.com, Dec 5 2017 

mmoroz, could you please update to RE2 commit 782df01? I suspect that Chromium doesn't have the \p and \P limit that I introduced a few weeks ago. Thanks!

Comment 4 by mmoroz@chromium.org, Dec 5 2017 

Sure, I'm on it!
Project Member

Comment 6 by bugdroid1@chromium.org, Dec 5 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/13bd9f72dd238f2c269c55af3fa07acf1d7ce68c

commit 13bd9f72dd238f2c269c55af3fa07acf1d7ce68c
Author: Max Moroz <mmoroz@chromium.org>
Date: Tue Dec 05 18:12:11 2017

[re2] Roll re2 4be7a14..5185d85.

Bug:  790735 
Change-Id: Ibf368a23b402dbe12c03afaed4032267abe52794
Reviewed-on: https://chromium-review.googlesource.com/808991
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521743}
[modify] https://crrev.com/13bd9f72dd238f2c269c55af3fa07acf1d7ce68c/DEPS

Comment 7 by junyer@google.com, Dec 6 2017 

Thank you, I have poked ClusterFuzz to retry.

Comment 8 by mmoroz@chromium.org, Dec 6 2017

Status: Fixed (was: Assigned)
CF will not recognize the fix quickly, as this crash has been marked as non reproducible:

>  The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.


But looking at the crash stats, it seems to be fixed. Closing!
►

Sign in to add a comment