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

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

Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and requesting some one from internals team to look in to this issue.

Thanks!

 Issue 825310  has been merged into this issue.

ClusterFuzz testcase 6411095275995136 is flaky and no longer crashes, so closing issue.

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

ClusterFuzz has detected this issue as fixed in range 550190:550191.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x05390000048b
Crash State:
  content::ZygoteHostImpl::Init
  content::BrowserMainLoop::EarlyInitialization
  content::BrowserMainRunnerImpl::Initialize
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=452642:452777
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=550190:550191

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

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.