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

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

Add more components for finding a right owner.

Looking at the code:
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/loader/HistoryItem.cpp?sq=package:chromium&dr=Ss&l=89

it looks benign. japhet@, who own that file and who the proper owner could be for this?

ClusterFuzz has detected this issue as fixed in range 549115:549116.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::HistoryItem::SetScrollOffset
  blink::FrameLoader::SaveScrollState
  blink::PaintLayerScrollableArea::UpdateScrollOffset
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523898:523900
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=549115:549116

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

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

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