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 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 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/+/7b9fe37fc214c456257f79ff6e9c76d37657100d (Revert "Logging to ensure that non-offscreen surfaces are destroyed as expected").

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.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7b9fe37fc214c456257f79ff6e9c76d37657100d (Revert "Logging to ensure that non-offscreen surfaces are destroyed as expected").

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.

Assert in SwiftShader code

Alexis, it looks like this was added as part of https://swiftshader-review.googlesource.com/2180 quite a while ago, but the assert wasn't hit until recent Chrome-side changes. Mind taking a closer look?

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

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  false
  es2::Device::stretchRect
  es2::Context::blitFramebuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523270:523295
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=559059:559067

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

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 6349581676445696 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.

ClusterFuzz testcase 6349581676445696 appears to be flaky, updating reproducibility label.

Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

ClusterFuzz has detected this issue as fixed in range 613661:613671.

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

Fuzzer: libFuzzer_gpu_swiftshader_fuzzer
Fuzz target binary: gpu_swiftshader_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  false
  es2::Device::stretchRect
  es2::Context::blitFramebuffer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523270:523295
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=613661:613671

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

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.

Possibly fixed by https://chromium-review.googlesource.com/1359821

Malay, would your change affect any glBlitFramebuffer calls?