Fix HostContextFactoryPrivate after GPU process restart |
||
Issue descriptionThis function doesn't quite work correctly. It's called to early and doesn't persist past the information past GPU process crashes. The following changes are needed: 1. Store |output_is_secure| in HostContextFactoryPrivate::CompositorData if there is a corresponding CompositorData in |compositor_data_map_|. On CompositorData construction |output_is_secure| should default to false. 2. In HostContextFactoryPrivate::ConfigureCompositor() call SetOutputIsSecure() with the stored value on the DisplayPrivatePtr. This should happen right after Resize() is called on DisplayPrivatePtr.
,
Sep 20
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/83526f9aef2fd6095c0f6bbab50438895323c22c commit 83526f9aef2fd6095c0f6bbab50438895323c22c Author: Sean Gilhuly <sgilhuly@chromium.org> Date: Thu Sep 20 14:22:58 2018 Persist calls to HostContextFactoryPrivate::SetOutputIsSecure Remember the last call to SetOutputIsSecure, and apply the information when the compositor is configured, or if the gpu process crashes. Bug: 882519 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Id212aaae3b2c164575c1d8e92e93e623bd182d69 Reviewed-on: https://chromium-review.googlesource.com/1225290 Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#592789} [modify] https://crrev.com/83526f9aef2fd6095c0f6bbab50438895323c22c/content/browser/compositor/viz_process_transport_factory.cc [modify] https://crrev.com/83526f9aef2fd6095c0f6bbab50438895323c22c/services/ws/host_context_factory.cc [modify] https://crrev.com/83526f9aef2fd6095c0f6bbab50438895323c22c/ui/compositor/host/host_context_factory_private.cc [modify] https://crrev.com/83526f9aef2fd6095c0f6bbab50438895323c22c/ui/compositor/host/host_context_factory_private.h
,
Sep 20
|
||
►
Sign in to add a comment |
||
Comment 1 by kylec...@chromium.org
, Sep 13