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/+/c7d741843e4398f385423b31abd87ffb08f3f5f4 (Defer connecting to GSA at startup.).

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.

No luck with reproduction (and at 1M it's difficult to make anything from the testcase alone.)

ClusterFuzz has detected this issue as fixed in range 560218:560219.

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

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

Crash Type: Abrt
Crash Address: 0x05390000599f
Crash State:
  blink::SVGTextLayoutEngine::LayoutTextOnLineOrPath
  blink::SVGTextLayoutEngine::LayoutInlineTextBox
  blink::SVGTextLayoutEngine::LayoutCharactersInTextBoxes
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=527606:527607
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=560218:560219

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

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

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