Regression: Tab does not get discarded after clicking on 'Discard a tab now' on chrome://discards page.
Reported by
db...@etouch.net,
Nov 23 2017
|
||
Issue descriptionChrome Version: 64.0.3276.0 Revision ccea2aa0a41cbb3dcbbf5961be4820d428b93a4c-refs/heads/master@{#518818}(32/64 bit) OS: Windows(7,8,10), Mac(10.12.6,10.13.2). Linux(14.1LTS) What steps will reproduce the problem? (1) Launch chrome, navigate to chrome://discards page (2) Click on 'Discard a tab now' and 'Urgent discard a tab now', observe. Actual: Tab does not get discarded after clicking on 'Discard a tab now' and 'Urgent discard a tab now'. Expected: Tab should get discarded. This is a regression issue, broken in 'M64', will soon update the other info: Good Build: 64.0.3275.0 Bad Build: 64.0.3276.0 You are probably looking for a change made after 518649 (known good), but no later than 518650 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/f74c4ebdabcfb1271337ae5cda7f017072174e95..c4453edb44d204b77378b3f885849d67fcdca3c0 Suspect : https://chromium.googlesource.com/chromium/src/+/c4453edb44d204b77378b3f885849d67fcdca3c0
,
Nov 27 2017
You'll note that despite the "Discarding a tab now" interstitial coming up, when the chrome://discards page reloaded, no tabs were actually discarded. This is because it's possible for no tabs to be currently eligible for automatic discarding, in which case the "discard" button is a no-op. The new WebUI doesn't load an interstitial, but rest assured the actual button is working, and in both cases, nothing is eligible for discard. Wait 10 minutes post restart and you'll see that tabs will become eligible for discard. |
||
►
Sign in to add a comment |
||
Comment 1 by rbasuvula@chromium.org
, Nov 23 2017