Restrict user navigation / exit unload flow to 500ms |
||||
Issue descriptionCurrently we have 1s limit on end-of-life handlers when the user navigates or closes a tab (pagevisibility, pagehide, unload, beforeunload) But it's 2s in practice due to bugs. We should restrict this to 500ms - which accommodates (sum of handlers) at 99.9th%ile UMA for duration of handlers on Windows stable (in milliseconds) 90th %ile: unload: .002; beforeunload: 0.28; pagehide: 0.004ms; vibilityhidden: 0.008 95th unload: .021; beforeunload: 1.4; pagehide: 0.006ms; vibilityhidden: 0.04 99th unload: 3.8; beforeunload: 14.3; pagehide: 0.75ms; vibilityhidden: 1 99.9th unload: 53; beforeunload: 272; pagehide: 5.3ms; vibilityhidden: 5.3
,
Sep 12
Issue 701434 has been merged into this issue.
,
Sep 12
,
Nov 8
,
Jan 2
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fbaa821f243a48ddbe53587336e14c00709537ee commit fbaa821f243a48ddbe53587336e14c00709537ee Author: kdillon <kdillon@chromium.org> Date: Wed Jan 02 22:07:57 2019 Restricting exit unload flow. Currently the limit on end-of-life handlers when the user navigates or closes a tab is 1s. This change restricts that to 500ms which accomodates at the 99.9th percentile. Bug: 832234 Change-Id: I09c9038dbe184910e44664e6d33b1b530c2645ae Reviewed-on: https://chromium-review.googlesource.com/c/1384790 Reviewed-by: Ken Buchanan <kenrb@chromium.org> Commit-Queue: Katie Dillon <kdillon@chromium.org> Cr-Commit-Position: refs/heads/master@{#619510} [modify] https://crrev.com/fbaa821f243a48ddbe53587336e14c00709537ee/content/browser/renderer_host/render_view_host_impl.cc
,
Jan 2
|
||||
►
Sign in to add a comment |
||||
Comment 1 by creis@chromium.org
, Jun 14 2018