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/+/177df647cdfd5e76e5eae86fdb0d1038e92fac4a (Make sure the offscreen framebuffer is never resized to zero.).

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/+/86d0abb79aaa0558dedac18fb78d5a3426641110

commit 86d0abb79aaa0558dedac18fb78d5a3426641110
Author: Geoff Lang <geofflang@chromium.org>
Date: Tue Nov 20 19:11:15 2018

Pass the correct have_context to GLES2Decoder::Destroy in the GPU fuzzer

ResetDecoder would always pass a true have_context to GLES2Decoder::Destroy
causing some assertions in the destuction of GL objects when the context
had previously been lost.

BUG= 877524 

Change-Id: I8b455ba0aa9515764d5caca63668401b09cb124e
Reviewed-on: https://chromium-review.googlesource.com/c/1344212
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609763}
[modify] https://crrev.com/86d0abb79aaa0558dedac18fb78d5a3426641110/gpu/command_buffer/tests/fuzzer_main.cc

ClusterFuzz has detected this issue as fixed in range 609762:609767.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0x1 == ::gl::g_current_gl_context_tls->Get()->Api->glIsSyncFn(sync_) in gl_fence
  gl::GLFenceARB::~GLFenceARB
  gl::GLFenceARB::~GLFenceARB
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=532611:532630
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=609762:609767

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

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

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