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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c416f80a900acf43478a6ad469ed0fa4af2e35aa (Refactor base::FuzzedDataProvider and fix the calling sites. The main goals:).

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.

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

commit f37b3414b0a0b7ffd99483661f6248aab711d60e
Author: Max Moroz <mmoroz@chromium.org>
Date: Tue Nov 27 20:32:49 2018

[net] Fix http2_frame_decoder_fuzzer not to pass nullptr to http2::DecodeBuffer constructor.

The same issue as the one fixed by https://crrev.com/c/1351286.

Bug:  908781 
Change-Id: Iba5696ebdebdc286949ab62b24e8c6464354e7d1
Reviewed-on: https://chromium-review.googlesource.com/c/1351948
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611290}
[modify] https://crrev.com/f37b3414b0a0b7ffd99483661f6248aab711d60e/net/third_party/http2/decoder/http2_frame_decoder_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 611282:611308.

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

Fuzzer: libFuzzer_net_http2_frame_decoder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  buffer != nullptr in decode_buffer.h
  http2::DecodeBuffer::DecodeBuffer
  http2_frame_decoder_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=610235:610237
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=611282:611308

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

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 6237673054011392 is verified as fixed, so closing issue as verified.

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