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/+/1f109d9c516640dda836493b24fd033da64411ff (Roll clang 328716:329921.).

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.

It's possible the clang roll changed something in msan of course, but someone who owns the code where the null-dereference occurred should probably take a look.

ClusterFuzz has detected this issue as fixed in range 555697:555698.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  blink::SlotAssignment::Trace
  blink::ScriptWrappable::Wrap
  blink::TextOffsetMapping::TextOffsetMapping
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=550607:550608
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=555697:555698

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

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

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