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/+/a210e801d2389b72e762a446be8651700a71b330 (Cluster fuzz RasterDecoder).

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 following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/390ffc84a086f23d502097da14fea80a68c1b795

commit 390ffc84a086f23d502097da14fea80a68c1b795
Author: Jonathan Backer <backer@chromium.org>
Date: Mon Jun 04 17:57:20 2018

Fix clusterfuzz bugs

We were hitting DCHECKS on bad user input. This is the wrong thing to do
with input from an untrusted client. This CL validates the user input
and sets a local GL error instead.

1) glTexStorage2D does not support compressed formats, so fail for ETC1

2) often cannot handle more than 1 level, so return an error instead of
   DCHECK

3) only call Texture::SetImmutable if a level was successfully defined

Bug:  844295 ,  844296 ,  844293 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I0db5de0508c555b50bb0f3eb379aa5d5bfdd4cc6
Reviewed-on: https://chromium-review.googlesource.com/1071711
Commit-Queue: Jonathan Backer <backer@chromium.org>
Reviewed-by: Victor Miura <vmiura@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564149}
[modify] https://crrev.com/390ffc84a086f23d502097da14fea80a68c1b795/gpu/command_buffer/service/raster_decoder.cc
[modify] https://crrev.com/390ffc84a086f23d502097da14fea80a68c1b795/gpu/command_buffer/service/raster_decoder_unittest.cc
[modify] https://crrev.com/390ffc84a086f23d502097da14fea80a68c1b795/gpu/command_buffer/service/raster_decoder_unittest_base.cc

I'm hoping this is fixed. It didn't repro locally. I'm going to close for now and hope that ClusterFuzz will reopen if it repros.

ClusterFuzz has detected this issue as fixed in range 564138:564162.

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

Fuzzer: libFuzzer_gpu_raster_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  gpu_raster_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=559059:559074
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=564138:564162

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

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.