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/+/df92bfed734a92c8f839af121218917ae599157d (cc::Surfaces for Video path handles null context_provider).

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.

Re-opening this as there are still crashes seen for 'cc::VideoResourceUpdater::CreateForSoftwarePlanes' on the latest Windows dev: 68.0.3432.3. 135 crashes from 117 clients so far.

Link to the list of the builds with crashes:
============================================
https://crash-procella.corp.google.com/browse?q=expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27cc%3A%3AVideoResourceUpdater%3A%3ACreateForSoftwarePlanes%27+AND+product.name%3D%27Chrome%27#productversion:1000,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50

lethalantidote@: Could you please take a look at these crashes.

Thank you!

Latest Android canary version: 68.0.3434.0 has reported 22 crashes from 20 clients so far.

 Issue 843962  has been merged into this issue.

Your bug is tagged as Release block Beta and we are branching in 2 days.Please have a fix ASAP.

This is only turned on for a finch experiment. 

 Issue 845486  has been merged into this issue.

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

commit c86905ed58620a39ecc5bb972eb599dbb8e6609f
Author: CJ DiMeglio <lethalantidote@chromium.org>
Date: Thu May 24 00:41:08 2018

Prevents SubmitSingleFrame while VFRP is uninitialized.

Currently, we are able to initiate a SubmitSingleFrame at any time.
This ignores two edge cases, both of which have us accessing
VideoResourceUpdater and VideoResourceProvider while they are null (which
means we never intialized VideoFrameResourceProvider (VFRP)).

Case one occurs when we call SubmitSingleFrame before we were able to
initialize VFRP the first time. The second can occur while we are
re-intializing VFRP on context loss.

Because we cannot just check if we have a context_provider to prove that
we are safe from these cases (it might be null because we are in software
compositing mode), we instead just check for the initialization.

Bug:  842471 
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: If3b31ed83908668ec21fbd0d2abbd7d45d454e67
Reviewed-on: https://chromium-review.googlesource.com/1069843
Reviewed-by: Justin Novosad <junov@chromium.org>
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561340}
[modify] https://crrev.com/c86905ed58620a39ecc5bb972eb599dbb8e6609f/third_party/blink/renderer/platform/graphics/video_frame_resource_provider.h
[modify] https://crrev.com/c86905ed58620a39ecc5bb972eb599dbb8e6609f/third_party/blink/renderer/platform/graphics/video_frame_submitter.cc

ClusterFuzz has detected this issue as fixed in range 561319:561343.

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

Fuzzer: ochang_media2
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  cc::VideoResourceUpdater::CreateForSoftwarePlanes
  cc::VideoResourceUpdater::CreateExternalResourcesFromVideoFrame
  cc::VideoResourceUpdater::ObtainFrameResources
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=557982:558008
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=561319:561343

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

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.