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:

Unify memory usage reporters of Oilpan into ThreadState. by peria@chromium.org - https://chromium.googlesource.com/chromium/src/+/62bfa3d4cbdfdfbfd7356e15e34c2aaa0036be74

Ability to return the height of fragmentainer groups that don't yet exist. by mstensho@opera.com - https://chromium.googlesource.com/chromium/src/+/3f96177578cf0511174d42546a70660cc8d6eeeb

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Looks most likely to be https://chromium.googlesource.com/chromium/src/+/3f96177578cf0511174d42546a70660cc8d6eeeb

I find it hard to believe that's the culprit, because the test case doesn't have multicol or any other kind of block fragmentation. Furthermore, I cannot bisect this, because I currently don't have access to a Linux machine, and I won't for the rest of the month either.

+various people who have touched `PaintLayerScrollableArea::UpdateScrollOffset` over the years. Can someone please take a look? Thanks!

No relevant changes in regression range, requesting re-run.

This could be related to accessibility, but it could also maybe be a gc issue related to the fact that PaintLayer::scrollable_area_ is a Persistent, which dates back to this CL:

https://codereview.chromium.org/1215973002

cc haraken and dmazzoni

Each time I request a bisct run it returns completely different ranges, months apart. Without a bisect or repro this isn't really actionable.

Could we get some help bisecting this please? 

ClusterFuzz has detected this issue as fixed in range 534596:534598.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::PaintLayerScrollableArea::UpdateScrollOffset
  blink::ScrollableArea::ScrollOffsetChanged
  blink::ProgrammaticScrollAnimator::ScrollToOffsetWithoutAnimation
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=430550:430572
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=534596:534598

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot