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/+/acc79f1cd39645d800757d7cfb09e4740a89ceab (Clamp contents visual overflow for LayoutSVGRoot).

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.

Looks like 11c6ace549bab9d81dfd5949ab4b5d02cb07a54c is the culprit (verified by reverting; also the TC contains "will-change: position").

Fix coming up shorty....

Reverting will-change: position cause of this. Nice job, clusterfuzz

https://chromium-review.googlesource.com/c/chromium/src/+/1365882

ClusterFuzz has detected this issue as fixed in range 614449:614472.

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

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

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000050
Crash State:
  chrome
  blink::SetStaticPositions
  blink::LineBreaker::SkipLeadingWhitespace
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=613675:613699
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=614449:614472

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

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

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