Using the provided regression range assigning to the possible suspect as per the change made for the file, “ThreadState.cpp”
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/0a027530722c328a13a992402e510f684e70dc24

@keishi -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

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

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

ClusterFuzz has detected this issue as fixed in range 521102:521144.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Stack-overflow
Crash Address: 0x00fa2000
Crash State:
  blink::ThreadState::MarkPhaseVisitRoots
  blink::ThreadState::CollectGarbage
  blink::ThreadState::ScheduleGCIfNeeded
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=506339:506361
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=521102:521144

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

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

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