Allow render-initiated freezing in resource coordinator |
||
Issue descriptionTabLifecycleUnit currently doesn't allow active -> frozen transitions, which are possible from the renderer when enabled with the stop-in-background feature. When this flag is enabled on desktop, freezing causes a DCHECK failure. This isn't currently an issue in the field since TabManager isn't enabled on Android, but will be needed going forward.
,
Jun 27 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a18d47428d64d9ae3b4138b2bb97d113c2c95646 commit a18d47428d64d9ae3b4138b2bb97d113c2c95646 Author: Scott Haseley <shaseley@google.com> Date: Wed Jun 27 02:10:50 2018 RC: Fix DCHECK failure on render-initiated freezing. Allow Active --> Frozen state transitions, but only from the renderer. This is the expected state transition for renderer-initiated freezing. Bug: 856266 Change-Id: I4aae9e3cba4c60d118e026fb185cf274a5645d58 Reviewed-on: https://chromium-review.googlesource.com/1113956 Reviewed-by: François Doray <fdoray@chromium.org> Reviewed-by: Fadi Meawad <fmeawad@chromium.org> Commit-Queue: Scott Haseley <shaseley@google.com> Cr-Commit-Position: refs/heads/master@{#570634} [modify] https://crrev.com/a18d47428d64d9ae3b4138b2bb97d113c2c95646/chrome/browser/resource_coordinator/tab_lifecycle_unit.cc
,
Aug 23
Effectively reverted in crrev.com/c/1182516. Render-initiated freezing is now only allowed on Android. |
||
►
Sign in to add a comment |
||
Comment 1 by fmeawad@google.com
, Jun 26 2018