Regression : Last two entries in 'Manage search engines' list appears after a delay in chrome://md-settings/ page.
Reported by
rp...@etouch.net,
Jun 9 2017
|
||||||||
Issue descriptionChrome Version: 61.0.3125.0 275810438db9694d4030c6b6390a0abe20618646-refs/heads/master@{#478135} OS: Windows (7,8,8.1,10) What steps will reproduce the problem? (1) Freshly launch chrome, navigate to chrome://md-settings/ and scroll down the page and click on 'Manage search engines' Actual: Last two entries in 'Manage search engines' list appears after a delay Expected: 'Manage search engines' list should appear properly This is a regression issue, broken in 'M-61', will soon update the other info: Good Build:61.0.3124.0 Bad Build: 61.0.3125.0
,
Jun 9 2017
Able to reproduce the issue on Mac 10.12.5, Windows 7 & Ubuntu 14.04 using latest Canary-61.0.3125.0. Manual Bisect: ------------ Good Build:61.0.3124.0-Revision-477839 Bad Build: 61.0.3125.0-Revision-478135 Per revision bisect info: ------------------------ You are probably looking for a change made after 477934 (known good), but no later than 477935 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/53a49d4c813bd76e1e38bfc890cfdc0d26da1f3d..cfd4fb5bd56f9e0f98668471a21f7f720cd5c311 alexclarke@,Please look into this issue & reassign if it is not related to your change. Thanks in advance..!!
,
Jun 9 2017
Strange, I'll take a look.
,
Jun 9 2017
,
Jun 12 2017
I tried to reproduce this in release mode and failed. It's always like the second video. I tried again in debug mode (very much slower) and I was able to reproduce this - however it still reproduces with the patch reverted. Still it's possible that scheduler changes might have cause this, so I took a trace. The way something like that might happen if the scheduler is to blame is if a task queue was getting throttled because the scheduler thought loading tasks for example are expensive and it was expecting user input. The trace showed that while the loading tasks and later timer tasks are deemed expensive, nothing was throttled. I don't think this patch is root cause.
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rp...@etouch.net
, Jun 9 2017