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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "PaintController.cpp" and observed there was some recent changes for the below file.

Suspect CL: 
https://chromium.googlesource.com/chromium/src/+/aa841d08d52baa416c0fb9d6ebe4a25cdb0dd915%5E%21/third_party/WebKit/Source/platform/graphics/paint/PaintController.cpp

wangxianzhu@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

This doesn't look like a recent regression. The crash (a CHECK failure) happens only with PaintUnderInvalidationChecking enabled. Lowering priority.

ClusterFuzz has detected this issue as fixed in range 537385:537399.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000004
Crash State:
  blink::PaintController::EndSubsequence
  blink::PaintLayerPainter::PaintLayerContents
  blink::PaintLayerPainter::Paint
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=518240:518474
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=537385:537399

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

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

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