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 does seem to be a real bug, with a FragmentData object pointing to itself as its next_fragment_.

But stack overflow is not P1.

ClusterFuzz has detected this issue as fixed in range 549099:549100.

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

Fuzzer: bj_broddelwerk
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc3ed57ff8
Crash State:
  ~FragmentData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=543289:543291
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=549099:549100

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

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

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