Issue metadata
Sign in to add a comment
|
Periodic 4-5 second delay for UI responsiveness when clicking the menu button, or entering a URL in the address bar
Reported by
jasz...@gmail.com,
Apr 30 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. Open Chromium 2. Click the menu button What is the expected behavior? Menu and URL auto-complete menus should respond within 1-15ms. What went wrong? Whenever Chrome is first launched, or after Chrome has been unfocused for a while, the UI takes several seconds to respond. This does not affect web pages. Did this work before? Yes Chrome 63, but not certain, its been this way since approx. December Chrome version: 66.0.3359.117 Channel: stable OS Version: Ubuntu 18.04 Bionic Flash Version: Tested with: - Google Chrome 66.0.3359.117, 66.0.3359.139 - Chromium 65.0.3325.181 - Linux kernel 4.15, 4.16 - Nvidia driver 390.48, 396.18 - Cinnamon 3.8 desktop
,
May 1 2018
,
May 2 2018
jaszhix@ Thanks for the issue. Tested this issue on Ubuntu 17.10 on the latest Stable 66.0.3359.139, latest Beta 67.0.3396.18 on Chrome and Chromium browsers and unable to reproduce the issue. On clicking on the three dot menu button, cannot observe any lag and Chrome is responding without any issues. Attached is the screen cast and chrome://gpu details for reference. As Ubuntu 18.04 is not available at TE end to confirm the issue, CC'ing thomasanderson@ who works on Linux issues for further help in triaging the issue. Thanks..
,
May 2 2018
OP, does the issue reproduce if you launch chrome with "google-chrome-stable --disable-gpu"?
,
May 3 2018
Yes, it does. Attached a trace in Chrome 66 with --disable-gpu passed.
,
May 3 2018
Looks like the hang is in RenderTextHarfBuzz::EnsureLayoutRunList. oshima@ I saw you added tracing to that function (back in 2015), so I'm assigning to you. Perhaps you know a better owner for this issue.
,
May 3 2018
thomasanderson@ Thanks for the update. As per comment #6, as this issue is assigned to oshima@ and the issue is reported on Ubuntu 18.04, which is not available at TE end for further testing and unable to reproduced the issue as mentioned in comment #3, adding TE-NeedsTriageHelp for further update on this issue. Thanks..
,
May 14 2018
the trace was added to tune the performance and 4 seconds is way too long. Adding a couple of folks who made changes to render text recently. I actually wonder if this change[1] is related. cjgrant@, can you look into this? [1] https://chromium-review.googlesource.com/c/chromium/src/+/865714
,
May 14 2018
Can you reproduce this in a fresh Chrome profile? (i.e. ProfileMenu -> Manage People -> add a user). One possibility might be that there is a bookmark in your profile with a page title that is either excessively long, or full of unicode characters (e.g. BiDi markers, other zero-width characters, or complex ligatures that are hitting pathological codepaths).
,
May 17 2018
oshima@, no, the CL in question could not have caused this issue. It pertains to a different omnibox implementation.
,
May 24 2018
I have time to work on this right now. I may be able to take a look a few ms later.
,
Jun 6 2018
Hi, just an update, I don't seem to be experiencing this issue anymore on Chrome 67 with Nvidia driver 396.24.02. What has changed is I re-installed Ubuntu 18.04 from a netboot ISO with little on it, so not sure if the issue would still persist on a full ISO image.
,
Jun 20 2018
,
Nov 19
*** UI Mass Triage *** Closing, since there is no updates since the past few weeks. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue.
,
Dec 14
Just an update, this issue reliably occurs on Linux Mint 19. When I reported the issue originally, I was running an alpha version of Mint 19 that wasn't in public circulation, and didn't think the distinction was important at the time because its based on Ubuntu 18.04, but it evidently is. That was a mistake on my part, so I am sorry for initially wasting your time trying to reproduce this on Ubuntu. I have been trying to figure out which change is causing this. Changing the org.cinnamon.desktop.interface font-name gsetting from Noto Sans 9 to Sans 9 does fix it - but when I apply the same mint settings on Ubuntu 18.04 as an override, recompile schemas, reset defaults, the issue doesn't occur. There is some other dependency within Mint causing this bug in Chromium, and so far from what I have tested, only Chromium and Google Chrome. This occurs on Nvidia, Mesa with Intel skylake graphics, and inside a VMware virtual machine. It occurs with and without hardware acceleration, and in the Mate desktop environment. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jasz...@gmail.com
, Apr 30 2018