New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 679139 link

Starred by 4 users
Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
lgrey@chromium.org
█ shrike@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome freezes for a few seconds every time i click in the omnibox

Project Member Reported by christandiono@google.com, Jan 7 2017 
Chrome Version       : 55.0.2883.95
OS Version: OS X 10.11.6
URLs (if applicable) : Any
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Have some text already in the omnibox (e.g. by visiting a website)
2. Click in the omnibox (e.g. to copy some text from it, edit the URL, etc.)

What is the expected result?
Chrome does not freeze for multiple seconds whenever I click in the omnibox

What happens instead of that?
Chrome freezes for multiple seconds whenever I click in the omnibox

Please provide any additional information below. Attach a screenshot if
possible.

This happened a few versions ago, then it stopped for a few versions, and now it is back. It happens in Guest mode and Incognito as well.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36

Comment 1 Deleted

Comment 2 by meh...@chromium.org, Jan 8 2017 

Is there any output from Chrome in the Console.app, when this happens?

Comment 3 by christandiono@google.com, Jan 8 2017 

Every time I click in the address bar, these show up in the logs, around the time Chrome unfreezes itself:

1/8/17 02:36:21.174 Google Chrome[6341]: +[NSXPCSharedListener endpointForListenerWithMessage:fromConnection:withListenerName:] timed out awaiting reply. Did the service fail to bootstrap itself? Is the system absurdly loaded?
1/8/17 02:36:21.174 Google Chrome[6341]: *** Assertion failure in -[NSLayerCentricRemoteView advanceToConfigPhase:awaitingWindowRights:], /Library/Caches/com.apple.xbs/Sources/ViewBridge/ViewBridge-159/NSRemoteView.m:3239
1/8/17 02:36:21.174 Google Chrome[6341]: Lookup: Unhandled exception 'NSInternalInconsistencyException' caught in -[LULookupDefinitionModule lookupAnimationControllerForString:range:options:originProvider:inView:]

Comment 4 by christandiono@google.com, Jan 8 2017 

Searching around a bit, it seems that this is due to the lookup feature in Mac OS X El Capitan (feature is described here: https://support.apple.com/kb/PH21573?locale=en_US).

Disabling this feature makes the problem go away.

Enabling this feature causes this problem to occur any time I try to lookup a word in Chrome (3 ways this happens: through ctrl+click->"look up", 3-finger tap, or force click), or indeed, any other program (I tried Finder and iTerm).

But for the Chrome omnibox specifically, it happens even with a normal click, without any special clicking. It couldn't possibly be that we're trying to lookup text whenever we click on it in the omnibox, right?

Comment 5 by meh...@chromium.org, Jan 8 2017

Cc: lgrey@chromium.org shrike@chromium.org
Components: UI>Browser>Omnibox
Thanks for your feedback. This is may be related to issue 627651?

Comment 6 by mpear...@chromium.org, Jan 8 2017 

Thanks for the report.

Do you happen to be clicking in the Omnibox using a Force Touch trackpad?

Comment 7 by christandiono@google.com, Jan 8 2017 

It does indeed seem related to or even the same as issue 627651.

Yes, I use a Force Touch trackpad.

Comment 8 by mpear...@chromium.org, Jan 9 2017

Mergedinto: 627651
Status: Duplicate (was: Unconfirmed)
Okay, as you use a force touch trackpad, this sounds identical to bug 627651.  I'm going to merge this one into that one.

According to that bug, if you update to MacOS 10.12, the issue should go away.  Please let us know if you decide to update and if the bug does or does not go away.
►

Sign in to add a comment