Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ec467a5f9ef29a0074681df178fb6a0c1ba42a96 (Reporting: Move JSON parsing into Delegate.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Looking now.

Found the problem, have a fix. Is there an easy way to test locally? (I'm not sure what the fuzzer test fixtures look like.)

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

commit 4ab6396bc9a783f5d0def6ca027830d46ec4c547
Author: Julia Tuttle <juliatuttle@chromium.org>
Date: Fri Feb 23 16:06:15 2018

Reporting: Fix header parser fuzzer.

The Reporting header parser expects to receive the result of parsing a
JSON list. The production code that calls it ensures this by wrapping the
normalized header value in square brackets, but my modification to the
fuzzer didn't. Now it does.

Bug:  815144 
Change-Id: I2f017c4be2ab39ce3c5b4fb0019b95a7b991b4b0
Reviewed-on: https://chromium-review.googlesource.com/934661
Commit-Queue: Julia Tuttle <juliatuttle@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538792}
[modify] https://crrev.com/4ab6396bc9a783f5d0def6ca027830d46ec4c547/net/reporting/reporting_header_parser_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 538791:538801.

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

Fuzzer: libFuzzer_net_reporting_header_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  is_list in reporting_header_parser.cc
  net::ReportingHeaderParser::ParseHeader
  net_reporting_header_parser_fuzzer::FuzzReportingHeaderParser
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=538536:538559
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=538791:538801

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 6443948630081536 is verified as fixed, so closing issue as verified.

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