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/+/1bb05e1810bb6117d6e091ceefe3b4ea17572971 (OOPIFs shouldn't invoke snap-to-min on PinchEnd.).

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.

ClusterFuzz has detected this issue as fixed in range 557984:557987.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in aligned_memory.cc
  base::AlignedAlloc
  cc::ListContainerHelper::CharAllocator::AllocateNewList
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=523878:523927
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=557984:557987

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

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 5260381162045440 is verified as fixed, so closing issue as verified.

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