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/+/840b7a60cc3c5f802ca271bd167e888e7494e8aa ([Re-Land] Use GPU Discardable in Image Decode Cache).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

 Issue 776268  has been merged into this issue.

We initialize the ServiceDiscardableManager before the command line in the fuzzers. Easy fix, I have a patch.

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

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

commit 1a72ba63243487773d433c75541a19098cce5d07
Author: Antoine Labour <piman@chromium.org>
Date: Tue Oct 24 22:05:18 2017

Fix gpu_*_fuzzer

They crash on startup because the ServiceDiscardableManager was initialized
before the command line. Easy fix.

Bug:  776267 
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ie4e4c4cac8bfc342cd13bbb424e0fa6f05bdf90a
Reviewed-on: https://chromium-review.googlesource.com/731376
Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511276}
[modify] https://crrev.com/1a72ba63243487773d433c75541a19098cce5d07/gpu/command_buffer/tests/fuzzer_main.cc

ClusterFuzz has detected this issue as fixed in range 511274:511297.

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000038
Crash State:
  base::CommandLine::HasSwitch
  base::CommandLine::HasSwitch
  base::SysInfo::AmountOfPhysicalMemory
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=509901:509932
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=511274:511297

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

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

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