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/+/77866ef44060aa415c0f94fe16658e037c53e5d2 (Better gn error message for missing target_os=chromeos).

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.

My CL just changes the error message in a GN assertion. It doesn't touch blink.

+cc some people who touched frame_selection.cc recently

Looks like the selection call is coming from printing code.

Bug 840257 looks very similiar. Merge into that one since there is a bit more discussion there?

Yeah, it's a dupe.

ClusterFuzz has detected this issue as fixed in range 557190:557193.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  LifecycleContext() in frame_selection.cc
  blink::FrameSelection::GetDocument
  blink::FrameSelection::ComputeVisibleSelectionInDOMTreeDeprecated
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=556205:556206
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=557190:557193

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

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.