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/+/51e1d9e7d6b6ce580fcdc5cb862038aba02e1bbf (hdr: Add auto-detection of HDR setting).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Assigning enne based on recent change:
https://chromium.googlesource.com/chromium/src/+/71acf7f01a747fcebf2d208261593f78242bc906
per the stack trace:
#5 0xeffbf053 in cc::PaintedScrollbarLayer::RasterizeScrollbarPart(gfx::Rect const&, gfx::Rect const&, cc::ScrollbarPart) cc/layers/painted_scrollbar_layer.cc:268

I'm assuming this is probably the same OOM crash from before, though.

ClusterFuzz has detected this issue as fixed in range 538633:538638.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x00000001
Crash State:
  [vdso]
  cc::PaintedScrollbarLayer::RasterizeScrollbarPart
  cc::PaintedScrollbarLayer::Update
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=508795:508884
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=538633:538638

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

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

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