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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/902cb209c7f227d4e116b9144ea1fbae9f3176b5 (disable http/tests/devtools/layers/layer-compositing-reasons.js).

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.

Surely disabling a test does not immediately introduce bugs

Kai, you're triaging a similar report - can you please handle this one too? Please duplicate if necessary. Thanks.

I actually let this run in the background earlier - I just checked on it, and it doesn't seem to have reproduced:

New crash type: Direct-leak
New crash state:
  FcPatternObjectInsertElt
  FcPatternObjectAddWithBinding
  FcPatternAppend

Original crash type: Null-dereference READ
Original crash state:
  width
  bool blink::WebGLRenderingContextBase::ValidateTexImageSubRectangle<blink::Image>
  blink::WebGLRenderingContextBase::TexImageImpl

This looks extremely similar to the other report, so I'm going to mark as duplicate.

ClusterFuzz has detected this issue as fixed in range 539061:539062.

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

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  width
  bool blink::WebGLRenderingContextBase::ValidateTexImageSubRectangle<blink::Image
  blink::WebGLRenderingContextBase::TexImageImpl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523443:523444
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=539061:539062

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

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.