mmoroz@: Referring to similar work done on  issue 694495  assigned to you, could you please take a look into it.

Looks like we need another re2 update :)

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

commit e0e3c52cbc129defc3e8b8e2ff20d16b63d15563
Author: mmoroz <mmoroz@chromium.org>
Date: Fri Mar 10 17:28:48 2017

Roll re2 db20d46..ae9cb49.

https://chromium.googlesource.com/external/github.com/google/re2.git/+log/db20d46..ae9cb49

TBR=tfarina@chromium.org, thakis@chromium.org
BUG= 700259 

Review-Url: https://codereview.chromium.org/2743883003
Cr-Commit-Position: refs/heads/master@{#456088}

[modify] https://crrev.com/e0e3c52cbc129defc3e8b8e2ff20d16b63d15563/DEPS

ClusterFuzz has detected this issue as fixed in range 456308:456310.

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

Fuzzer: libfuzzer_third_party_re2_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=453388:453440
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=456308:456310

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95LmfWPTrHu-scZ9KcuNK9KiqGxIEOsnpDvLnsD6KtvrfRBRBw1m97S1zKEMLQIsVYrXq295udWnscZ8wF4KwAX1m4Z_GgqScS-9Adtf-dZ77-wcxuoclTqKcG7ZqE9GmoA4GlnagRFcZ-U_BWf_cXROZWVuacXhKr08jOFS7paKEJ3A_NIntatMEnKBlFjUw5S7n8c03GtRzgklRKYTsZ6qbE0o7JQUidcaePTeHpv0ZirNm1DvImE7dtKOMdXtOOsmBqu9MbLGRhCr4SZNSRr_0X9BLCIc-OkHbBCcfKGBWXg3oIB0VcAw3sM-LFjfue8dCNumlSgk51R3huNQD8Tigr8_S8oEP_EdEwajKI7Hg0skf0?testcase_id=5505843681558528


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.

ClusterFuzz testcase 5505843681558528 is verified as fixed, so closing issue.

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