Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

This looks like a paint-related issue, that would be setting a mask layer that has mismatched bounds (this comes directly from blink).
No obvious culprit in the regression range though.

Could pass it to me too, though I will not get a chance to look for a while.

Likely related to composited border radius. I think this is not very important because the test case involves some insane radius value. We probably failed to clamp or round layer bounds somewhere.

ClusterFuzz has detected this issue as fixed in range 569916:569917.

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

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

Crash Type: CHECK failure
Crash Address: 
Crash State:
  bounds().ToString() == mask_layer()->bounds().ToString() in layer.cc
  cc::Layer::PushPropertiesTo
  cc::PictureLayer::PushPropertiesTo
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=533114:533124
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=569916:569917

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

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

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