New content rendering timeout interferes with deterministic rendering |
||
Issue descriptionIn e.g. some headless environments, we care about deterministic rendering results. The new content timeout in RenderWidgetHostImpl can affect the page rendering by removing the active CompositorFrame in its frame sink. This interferes e.g. with the --run-all-compositor-stages-before-draw mode, where we long delays between CompositorFrame submissions are common. Therefore, we'd like a way to disable the new content timeout, e.g. via a command line flag.
,
Oct 19 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Oct 19 2017