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 suspected regression changelists:

Fixing post merge nit (comment only). by ahemery@chromium.org - https://chromium.googlesource.com/chromium/src/+/54c70ea07f851ca902096f6559d5efdfaa485c9b

Transmit the response's body datapipe in CommitNavigation(). by arthursonzogni@chromium.org - https://chromium.googlesource.com/chromium/src/+/7521deccbb7d3d4a7700e6e007e679a8706d8be0

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Fixed because my CL has been reverted in the meantime.
I need to take a look at this reproducer before trying to commit it again.

ClusterFuzz has detected this issue as fixed in range 573375:573394.

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

Fuzzer: puzzor
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  mojo::PipeControlMessageHandler::IsPipeControlMessage
  IPC::ChannelAssociatedGroupController::Accept
  mojo::Connector::ReadSingleMessage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=573275:573280
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=573375:573394

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

See https://github.com/google/clusterfuzz-tools 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 6491730313216000 is verified as fixed, so closing issue as verified.

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