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/+/b194ab9a36a8178ed2ef41da9e109b880d5ac62b (Make falures to stop RemoteTestServer fatal.).

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.

ClusterFuzz has detected this issue as fixed in range 616877:616900.

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

Fuzzer: afl_net_http_server_fuzzer
Fuzz target binary: net_http_server_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000013e
Crash State:
  net_http_server_fuzzer
  net::WebSocketEncoder::Inflate
  net::WebSocketEncoder::DecodeFrame
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=616454:616490
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=616877:616900

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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