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/+/c077cf688813825c78d697ff715633345bb7691e (Merge MediaElementEventQueue into EventQueueImpl).

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.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/46958cb3b10917f4960a3a24d5e697e25f3dbe54

commit 46958cb3b10917f4960a3a24d5e697e25f3dbe54
Author: Hajime Hoshi <hajimehoshi@chromium.org>
Date: Fri Jun 22 07:01:51 2018

Add check the absence of execution context at EventQueue constructor

The check existed at MediaElementEventQueue, but I lost this when
merging this into EventQueueImpl at https://chromium-review.googlesource.com/c/chromium/src/+/1098742
This CL adds this check again.

Bug:  854892 ,  854775 
Change-Id: I0f851fbb3514c3ce59622f1accdaaa9743e316a0
Reviewed-on: https://chromium-review.googlesource.com/1109594
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569546}
[modify] https://crrev.com/46958cb3b10917f4960a3a24d5e697e25f3dbe54/third_party/blink/renderer/core/dom/events/event_queue.cc

ClusterFuzz has detected this issue as fixed in range 569545:569547.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::EventQueueImpl::EnqueueEvent
  blink::HTMLMediaElement::ScheduleEvent
  blink::HTMLMediaElement::SelectMediaResource
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=568764:568769
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=569545:569547

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

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

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