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/+/9a923f285819a3c22acec7750382acf5be69e3e2 (Pass approprite task runners to Binding::Bind and InterfacePtr::Bind via URLLoaderClientImpl).

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 content was only 

<!-- /LayoutTests/external/wpt/workers/interfaces/DedicatedWorkerGlobalScope/postMessage/setting-postMessage.html 

Does this really cause the crash? (I couldn't reproduce this on my local machine)

ClusterFuzz has detected this issue as fixed in range 577815:577816.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !response_.IsNull() in document_loader.cc
  blink::DocumentLoader::DataReceived
  blink::Resource::AppendData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=546456:546457
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=577815:577816

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

Additional requirements: Requires Gestures

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

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