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

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

Apparently, the Maybe<> object returned here can be empty: https://chromium.googlesource.com/chromium/src/+/20cce4645adf844a80fa798ce854e53edb8455e9/third_party/WebKit/Source/bindings/core/v8/ScriptPromise.cpp#202

Assigning to Blink people. PTAL.

ClusterFuzz has detected this issue as fixed in range 533646:533647.

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

Fuzzer: v8_builtins_generator
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000001
Crash State:
  blink::ReportFatalErrorInMainThread
  v8::V8::FromJustIsNothing
  blink::ScriptPromise::InternalResolver::Reject
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=530470:530474
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=533646:533647

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

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

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