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

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

Predator could not provide any possible suspects.

From the below CL observing some changes related to 'editing' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/5830b993a3529bf00e2149afc0c0b3d268d78d36..2b47df6d9d7f4cf3e5ba2a493b8a1e80aebeb3c4?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/bfc75c0a27fff772ed4d96ef40dfd6f127ee29fa

lushnikov@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 551573:551577.

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

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

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::EditingIgnoresContent
  blink::PositionTemplate<blink::EditingAlgorithm<blink::NodeTraversal> >::FirstPo
  blink::TextDirection blink::DirectionOfEnclosingBlockOfAlgorithm<blink::EditingA
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=523880:523906
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=551573:551577

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

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

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