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/+/374d0f6b15610eada09f473761de4615fdb64652 ([LayoutNG] Unify selection start/end API into LayoutTextSelectionStatus.).

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.

This crash is caused by shadow v0, sync mutation event and selection.
The case is very rare in wild.

This crash started during M68 time frame and still occurs in latest canary-72.0.3584.0 with single digit instances. 

Link to the builds which introduced the crash
=============================================
https://crash.corp.google.com/browse?q=product_name%3D%27Chrome%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27renderer%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27blink%3A%3ALayoutSelection%3A%3AComputeSelectionStatus%27#-productname:1000,productversion:1000,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50

yoichio@ would it be possible to have a fix to avoid spikes in future.

Issue 895774 has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 620890:620891.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  storage_.is_populated_ in optional.h
  _ZNR4base8OptionalIjE5valueEv
  blink::LayoutSelection::ComputeSelectionStatus
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=587084:587085
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=620890:620891

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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