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 the code search for the file, “frame_loader.cc” assigning to concern owner from GIT revision log.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/df3ea35f363255ed60698f5e951522beac51c7c0

@dgozman -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

The repro case fails for me in debug in "avformat_find_stream_info". 

Interestingly, it does not fail without <video> tag in the attached repro. Could this be a media issue? CC'ing alokp@ and servolk@ who had commits in media/filter in the regression range.

ClusterFuzz has detected this issue as fixed in range 569503:569504.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::WebDocumentLoaderImpl::DetachFromFrame
  blink::FrameLoader::StartLoad
  blink::FrameLoader::LoadInternal
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=399234:399406
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=569503:569504

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

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

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