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/+/17b41949b785cb505750e0b65e9f441391283ef4 (Harmonize the sandbox memory limit across platforms.).

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.

My CL in #2 is completely unrelated to Skia.

Likewise, this bug has nothing to do with Skia.  It is just Skia catching a much higher level OOM as far as I can tell- malloc fails, we abort.  As with all of these, I spent a little time looking into the calling code and don't see any recent changes, so the suspect, if CF is wrong, is also unfortunately unknown to us.

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

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  sk_abort_no_print
  SkBitmap::allocN32Pixels
  cc::PaintedScrollbarLayer::RasterizeScrollbarPart
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=573556:573557
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=587601:587602

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

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

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