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.

ClusterFuzz has detected this issue as fixed in range 559059:559067.

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

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=559059:559067

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

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

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

https://chromium.googlesource.com/chromium/src/+/a210e801d2389b72e762a446be8651700a71b330 (in the progression range) landed which changes the interpretation of the "config" bits, causing the repro cases to not apply any more (we temporarily lost coverage). CF would eventually restore coverage, but in the mean time let's reopen.

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

commit 88dc7697dc9b701aec079ed790a5fb5d7336708b
Author: Geoff Lang <geofflang@chromium.org>
Date: Tue Aug 21 21:38:35 2018

Invalidate the fence used in async read pixels if the context is lost.

BUG= 841655 

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: I2d112cfc5262e02963d1151f19f721cd84fa756f
Reviewed-on: https://chromium-review.googlesource.com/1181178
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584901}
[modify] https://crrev.com/88dc7697dc9b701aec079ed790a5fb5d7336708b/gpu/command_buffer/service/gles2_cmd_decoder_passthrough.cc