Assigning to the concern owner from Predator results--
The result is a list of CLs that change the crashed files. 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/d8778253872afdde9536565400d38bb4defeeb85
Time: Sun Aug 07 11:44:17 2016
Lines 673 of file prog.cc which potentially caused crash are changed in this cl (frame #5, "re2::Prog::MarkSuccessors"). 

Lines 1211, 1223-1227 of file compile.cc which potentially caused crash are changed in this cl (frame #7, "re2::Compiler::Finish"; frame #9, "re2::Regexp::CompileToProg"). 

File re2.cc is changed in this cl (and is part of stack frame #10, "re2::RE2::Init"; frame #11, "re2::RE2::RE2")
Minimum distance from crash line to modified line: 0. (file: compile.cc, crashed on: 1211, modified: 1211). 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/7906344578cb22002cda5d6f7085d12959df2887
Time: Mon Feb 13 06:49:32 2017
Lines 672-703 of file prog.cc which potentially caused crash are changed in this cl (frame #5, "re2::Prog::MarkSuccessors"). 

Lines 1213 of file compile.cc which potentially caused crash are changed in this cl (frame #7, "re2::Compiler::Finish").
Minimum distance from crash line to modified line: 0. (file: compile.cc, crashed on: 1213, modified: 1213). 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/33114d19ec3acc1bed077c7091b255cc1b021604
Time: Fri May 13 05:21:31 2016
Lines 1213 of file compile.cc which potentially caused crash are changed in this cl (frame #7, "re2::Compiler::Finish").
Minimum distance from crash line to modified line: 0. (file: compile.cc, crashed on: 1213, modified: 1213). 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/565fcac8a79225d34f4573d15d103cca0992a27e
Time: Fri May 13 06:26:52 2016
Lines 1198 of file compile.cc which potentially caused crash are changed in this cl (frame #8, "re2::Compiler::Compile"). 

File prog.cc is changed in this cl (and is part of stack frame #5, "re2::Prog::MarkSuccessors"; frame #6, "re2::Prog::Flatten")
Minimum distance from crash line to modified line: 0. (file: compile.cc, crashed on: 1198, modified: 1198). 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/da1249d9b5f34f3f8170d07ee5869b510eb477d0
Time: Fri Sep 09 06:00:28 2016
Lines 233-240 of file re2.cc which potentially caused crash are changed in this cl (frame #10, "re2::RE2::Init"). 

File prog.cc is changed in this cl (and is part of stack frame #5, "re2::Prog::MarkSuccessors"; frame #6, "re2::Prog::Flatten")
Minimum distance from crash line to modified line: 0. (file: re2.cc, crashed on: 233, modified: 233). 

Author: Paul Wankadia
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/0c31e94bc0f8254fad960977d610b7560114ae34
Time: Wed Mar 02 02:52:19 2016
Lines 231-236 of file re2.cc which potentially caused crash are changed in this cl (frame #10, "re2::RE2::Init").
Minimum distance from crash line to modified line: 0. (file: re2.cc, crashed on: 231, modified: 231). 

Author: RIchard Kralovic
Project: chromium-re2
Changelist: https://chromium.googlesource.com/external/github.com/google/re2.git/+/eb00dfdd82015be22086cacc6bf830f72a10e2bc
Time: Tue Mar 01 15:25:15 2016
Lines 230-240 of file re2.cc which potentially caused crash are changed in this cl (frame #10, "re2::RE2::Init").
Minimum distance from crash line to modified line: 0. (file: re2.cc, crashed on: 230, modified: 230).


Suspecting Commit#
https://chromium.googlesource.com/external/github.com/google/re2.git/+/0c31e94bc0f8254fad960977d610b7560114ae34

@Paul Wankadia -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

The reproducer testcase is \PS{940}…, which should have been rejected during parsing. Is Chromium fuzzing with -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION? (Please loop in kcc and mmoroz if necessary.)

Adding few Devs as per Comment#2.
Thank You.

Ping, kcc! :)

Does Chromium need -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION too?

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=695292, 
hopefully Max or Oliver can handle it soon.

Looks like we also need to update re2 revision once again.

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

commit ce2ff44b62a49ace0153ad19023fcd95e8be4312
Author: mmoroz <mmoroz@chromium.org>
Date: Thu Feb 23 11:46:36 2017

Roll re2 193486d..db20d46.

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

BUG= 694495 

TBR=tfarina@chromium.org,thakis@chromium.org,ochang@chromium.org,

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

[modify] https://crrev.com/ce2ff44b62a49ace0153ad19023fcd95e8be4312/DEPS
[modify] https://crrev.com/ce2ff44b62a49ace0153ad19023fcd95e8be4312/third_party/re2/README.chromium

ClusterFuzz has detected this issue as fixed in range 452447:452474.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4732288891092992

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://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=450345:450369
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=452447:452474

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv956HHypr1a8BeP8tcoJrMsp4CzrWUqeyltsBFMYWHSRLt-Y3xkxSDGD944x-H86hSxJz7_ifYdMjp9dpRgbkaAJM9pXnlR-qTXeSy9BAnSqdn8LLUtFUB2TrahmPTwOv7tsJAcB8iaoQc23fBp8d5CHs1qJZJ8uDAdnYftzVF1u_P6_IXnkjwXn7G7oAZvyLW6rDElviUg-qjdmbip3kSJnRcim9sgyDkEQRb1RKS_1k-LYaw3KV9T7cjE0WzfGcD9Ff72o-eYxgxjK_ays0QnR7n8ZrHA97Gck62PHITPORZxoHwJvu_5yYxo5r6pOy0-u-I_8bZqitUII_IWoTBtIAQaogJNQR7PtczqRkzN-UJRVfyVdlJsRdYc2MUwLzL6Yi9dkTPSQgQVM7nHBXpvSMxQMYQ?testcase_id=4732288891092992


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.

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

commit 0ec18db7916d7549ee8fe61bb6063ca8922ed86e
Author: mmoroz <mmoroz@chromium.org>
Date: Fri Feb 24 09:55:20 2017

Use -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION for libFuzzer and AFL.

R=kcc@chromium.org, ochang@chromium.org
BUG= 695292 , 694495 

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

[modify] https://crrev.com/0ec18db7916d7549ee8fe61bb6063ca8922ed86e/build/config/sanitizers/BUILD.gn
[modify] https://crrev.com/0ec18db7916d7549ee8fe61bb6063ca8922ed86e/build/config/sanitizers/OWNERS
[modify] https://crrev.com/0ec18db7916d7549ee8fe61bb6063ca8922ed86e/build/config/sanitizers/sanitizers.gni

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

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