Issue metadata
Sign in to add a comment
|
chrome freezes for ~3 seconds after performing basic actions
Reported by
dkert...@zendesk.com,
Dec 5
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: 1. Launch Chome 2. Notice stutter while the basic UI is rendered 3. Open a new tab, or window, or open the About or Settings pages What is the expected behavior? Immediate UI response, no delays What went wrong? Since the previous version of Chrome the UI has started to become unresponsive after performing very basic actions, like opening a new tab. The entire UI freeze and the rendering of the UI elements stutters. The problem persist after uninstalling Chrome and deleting all the local settings and data. The problem persist even before signing in into Google. Did this work before? Yes 69.0.3497 or 2 versions before 71.0.3578.80 Chrome version: 71.0.3578.80 Channel: stable OS Version: OS X 10.13.6 Flash Version: Interestingly enough the problem does NOT shows if I launch Chrome from the terminal, as in: $ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome Chrome's output in the terminal shows a lot of these 2 messages: [45904:775:1205/111033.922742:ERROR:native_view_host_mac.mm(199)] Not implemented reached in virtual void views::NativeViewHostMac::ShowWidget(int, int, int, int, int, int) [45904:775:1205/111043.560494:ERROR:web_contents_view_mac.mm(487)] Failed to look up NSViewBridgeFactoryHost!
,
Dec 6
Tried testing the issue on reported chrome version #71.0.3578.80 using Mac OS 10.13.6 by following below steps. Steps: ===== 1.Launched chrome. 2.Opened new tabs and windows. 3.Navigated to About or Settings pages. 4.Unable to observe any delay and unresponsive after performing above basic actions. 5.Tested by installing M-71 stable over M-70 as well and didn't observe any chrome freeze Attached screencast for reference. cc'ing tapted@(chromium//src/ui/views/controls/native/OWNERS) based on the terminal output from the reporter. Thanks.!
,
Dec 6
Hi, thanks a lot for testing my bug report. After reading your comment I tried to further troubleshoot my issue by looking for any local configuration or third-party software that could be interfering with Chrome; what I found is that by forcing an upgrade for a security software (antivirus) the issue with Chrome was resolved. I highly suspect that my issues was caused by some weird interaction between this antivirus software and Chrome, but unfortunately I can't really tell how due to all the security mechanism of macOS. You can consider this ticket solved on my side, thanks!
,
Dec 7
#3: Thanks for the update. Just in case we get other similar reports, what antivirus software is that? And do you happen to know what the old version you had was? Marking this bug WontFix, but please do reply :)
,
Dec 9
The antivirus is Confer / Carbon Black and the problem was with a version before 3.2.2.6; unfortunately I don't know what specific version I was running before the upgrade. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 5