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

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

Assign this to nhiroki@ for triage.  Looking at the following code, is this an intentional crash?


static void ReportFatalErrorInWorker(const char* location,
                                     const char* message) {
  // FIXME: We temporarily deal with V8 internal error situations such as
  // out-of-memory by crashing the worker.
  LOG(FATAL);
}

ClusterFuzz has detected this issue as fixed in range 583579:583580.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  blink::ReportFatalErrorInWorker
  v8::Function::Call
  blink::V8ScriptRunner::CallFunction
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=571655:571657
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=583579:583580

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

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.