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 suspected regression changelists:

Harden against X11 instability. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/fbba4900f68b12171277175980df2e52517cb6b6

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

This crash occurs very frequently on linux platform and is likely preventing the fuzzer inferno_layout_test_unmodified from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

Similar to or duplicate of  Issue 861882 .

M69 branch is coming VERY soon on July 19th, Your bug is marked as ReleaseBlock-Beta for M69. Please try to land the fix ASAP to trunk in order to prevent many merges going after M69 branch. This will also help us to branch M69 from high quality trunk. Thank you.

Since it is related to Swiftshader component,hence assigning it to capn@ for further triage.

ClusterFuzz has detected this issue as fixed in range 575069:575074.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900007e14
Crash State:
  sw::FrameBufferX11::validateWindow
  sw::FrameBufferX11::~FrameBufferX11
  sw::FrameBufferX11::~FrameBufferX11
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=573289:573290
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=575069:575074

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.