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, "harf_buzz_shaper.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/7b20499fff2b1a299551ecf8ea8e9fbcf104e1a9%5E%21/third_party/WebKit/Source/platform/fonts/shaping/HarfBuzzShaper.cpp

gyuyoung@ -- 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!

ClusterFuzz has detected this issue as fixed in range 550183:550208.

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

Fuzzer: bj_broddelwerk
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff5bdd7a48
Crash State:
  blink::ScriptRunIterator::ScriptRunIterator
  blink::HarfBuzzShaper::Shape
  blink::HarfBuzzShaper::Shape
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=544013:544015
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=550183:550208

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

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.

Hmm, I believe the CL should not make an issue because it just replaced RefPtr with scoped_refptr. If this is a real crash, let me take a look.

ClusterFuzz testcase 5668127908823040 is verified as fixed, so closing issue as verified.

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