Clean up tab nodes aggressively behind feature toggle
A new feature toggle is introduced to influence how TabNodePool::CleanupTabNodes() issues deletions of tab nodes (i.e. sync entities for SESSIONS). The new mode is very aggressive and is conceptually similar to removing the notion of 'free' nodes, although this is not obvious in the code because it depends on how TabNodePool is used by upper layers (i.e. FreeTab() is followed closely by CleanupTabNodes() for the local session, in SyncedSessionTracker::CleanupLocalTabs()). The risk that this mode (disabled by default) entails is that closed tabs may never have the chance to sync, so if the user closed the tab accidentally, or expected to see the tab in other devices, it would be a regression. This doesn't seem very realistic, so let's experiment via Finch and assess the impact of the change. Bug: 882489 Change-Id: I76609434e5a733b8b5e4c94820ef2f29dd862ce5 Reviewed-on: https://chromium-review.googlesource.com/c/1264597 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#597085}
Showing
Please register or sign in to comment