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 adding ccs based on suspected regression changelists:

Apply root element's scroll-behavior to the viewport. by sunyunjia@chromium.org - https://chromium.googlesource.com/chromium/src/+/4bd9033d09cb618c71d5714222ba1c9029d168fa

Fix mid-word-break to handle grapheme clusters by kojii@chromium.org - https://chromium.googlesource.com/chromium/src/+/85b84a4d900effddac4b32e7774d23f51fd562e0

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

sunyunjia@ / kojii@ Could you please look into this issue.

Thank You...

I don't think mine is related, it's a change to the line breaker. Sorry.

I couldn't reproduce the crash on Stable 63.0.3239.108, are there any instructions?

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.


Thank You...

ClusterFuzz has detected this issue as fixed in range 535623:535664.

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

Fuzzer: inferno_twister
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x0000000000d0
Crash State:
  blink::Page::GlobalRootScrollerController
  blink::LocalFrameView::MaximumScrollOffsetInt
  blink::ScrollableArea::MaximumScrollOffset
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=497420:497434
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=535623:535664

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

Additional requirements: Requires HTTP

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

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