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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3f921557c4cb83453bfce0fe8637e489a90064ad (Drop UseCounter usage measurement on view-source pages.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Bisected to https://chromium.googlesource.com/chromium/src/+/aadc264de1e60a3490b61f2df6193b64dd164ac9

yoichio, could you please take a look?
Thanks

The patch I downloaded was asan-linux-debug-508996

ClusterFuzz has detected this issue as fixed in range 547640:547641.

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

Fuzzer: marty_html_twiddler
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  layout_object->CanBeSelectionLeaf() in LayoutSelection.cpp
  blink::CalcSelectionRangeAndSetSelectionState
  blink::LayoutSelection::Commit
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=547640:547641

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

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

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