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/+/0b2c8bc98b2ad9daa14e456e0a777f6f48f6a1aa ([LayoutNG] flag-specific rebaselines for css/ and css3/).

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.

The CL changes only test expectation files and no code changes. Can you try to find other possible CLs?

ClusterFuzz has detected this issue as fixed in range 558200:558201.

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

Fuzzer: marty_html_twiddler
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  base::CreateThread
  CreateNonJoinableWithPriority
  base::PlatformThread::CreateNonJoinable
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=546509:546510
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=558200:558201

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

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.

ClusterFuzz testcase 4956377253150720 is verified as fixed, so closing issue as verified.

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