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

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

This seems like a dupe, but not sure of what.

ClusterFuzz has detected this issue as fixed in range 616332:616334.

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

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

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (old_visual_rect_.IsEmpty() && new_visual_rect.IsEmpty()) || object_.EnclosingLa
  blink::FindVisualRectNeedingUpdateScopeBase::CheckVisualRect
  blink::FindVisualRectNeedingUpdateScope::~FindVisualRectNeedingUpdateScope
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=616332:616334

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

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

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