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 and CL could not provide any possible suspects.

Using Code Search for the file, "LayoutObject.cpp" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/0a000da0e2e2e73eee4041e9ec1247edea576930

chrishtr@ -- 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 527016:527020.

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

Fuzzer: mbarbella_webcomponents
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::LayoutObject::Container
  blink::LayoutBox::LocationContainer
  blink::LayoutBox::OffsetFromContainer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=526971:526973
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=527016:527020

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

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

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