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/+/ad8ab8fd70189c757e710a5b7335c8bf8be7188b (viz hit test: Add a fuzzer for hit-test-query.).

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.

+rockot@ for advice: any suggestion on how to fix/suppress the leaks with mojo::edk::Init()? I found other fuzzers that do mojo::edk::Init [1, 2], but not sure how those addressed leaks.

[1] https://cs.chromium.org/chromium/src/components/webcrypto/fuzzer_support.cc?l=28
[2] https://cs.chromium.org/chromium/src/tools/ipc_fuzzer/message_replay/replay_process.cc?l=68

As commented on the CL, just don't initialize it more than once.

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

commit 35438ebd0d7fad68480014abfd437f30d9f10dd5
Author: Sadrul Habib Chowdhury <sadrul@chromium.org>
Date: Sun Mar 11 22:04:24 2018

viz/fuzzer: Fix a memory leak in the HitTestQuery fuzzer.

The environment needs to be set up only once for all runs, instead
once for every run.

BUG= 820371 

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I54f4ccce8349b58f6d1bf67fa801e4181db1b119
Reviewed-on: https://chromium-review.googlesource.com/958227
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542404}
[modify] https://crrev.com/35438ebd0d7fad68480014abfd437f30d9f10dd5/components/viz/host/hit_test/hit_test_query_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 542403:542404.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  mojo::edk::Init
  mojo::edk::Init
  hit_test_query_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=541967:541981
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=542403:542404

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

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

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