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:

Implement GL_MAX_PROGRAM_TEXEL_OFFSET and GL_MAX_TEXTURE_LOD_BIAS by sugoi@google.com - https://swiftshader.googlesource.com/SwiftShader/+/0e22d3ac1342803e4f6e99dee0b1bc7638f0acdc

glGetFragDataLocation implementation by sugoi@google.com - https://swiftshader.googlesource.com/SwiftShader/+/b3f5ed7a0986d906c4f70cbf86076d9b4ec11964

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

sugoi@ Could you please look into this issue...

Couldn't reproduce a leak in SwiftShader (libGLESv2.so or libEGL.so). Only got several in chrome.

ClusterFuzz testcase 5803513008095232 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 587598:587602.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  es2::Buffer::bufferData
  allocateRaw
  sw::allocate
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=535470:535472
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=587598:587602

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

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.

Assuming this was fixed by https://chromium-review.googlesource.com/1194698, which would mean it was a Clang bug. We may also see this re-appear if the Clang upgrade simply changed the stack trace signature.