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

Issue 799009 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 777863
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

NSTrackingArea error on external link click

Reported by lucas.jo...@starlingbank.com, Jan 4 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. Click link in an external program (eg Slack)

What is the expected behavior?
A new window with the link should appear

What went wrong?
When you click on a link in an external program, like Slack, a new chrome instance is created and automatically closes, and a new chrome window is opened. This error persists despite reinstalling and clearing the Application Support folder. The error affects all applications.
The exact error thrown is from Google Chrome (AppKit):
*** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug.

Did this work before? Yes Unknown

Chrome version: 63.0.3239.108  Channel: stable
OS Version: OS X 10.13.2
Flash Version:
 
chrome-error-smaller.mov
2.7 MB Download
Labels: Needs-Bisect Needs-Triage-M63
Components: UI>Browser
Labels: -Needs-Bisect M-65 Triaged-ET
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.1 using chrome reported version #63.0.3239.108 and latest chrome version #65.0.3311.0. Observed that on clicking link in slack, open the link in chrome window with error in console as "*** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug".
But unable to provide bisect results as upon installing chrome version M52 or M50 and clicking link in slack open the link in chrome window having chrome version #62.0.3202.94 instead of M52. Hence, unable to get good and bad build range.

Attached a screen cast for reference.
Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
799009.mp4
3.8 MB View Download

Comment 3 by tapted@chromium.org, Jan 12 2018

Cc: krajshree@chromium.org
Do you have anything in chrome://crashes ? Or can someone that can repro provide one?

And can anyone reproduce on 10.12 ?

This might be Issue 795738.

I couldn't reproduce in 10.13.2 (17C205), but there crashes on Issue 795738 for that OS version. Tested 63.0.3239.132

Comment 4 by tapted@chromium.org, Jan 12 2018

Labels: Needs-Feedback

Comment 5 by tapted@chromium.org, Jan 17 2018

I suspect this is related to  Issue 777863  and the NSTrackingArea thing is a red herring

Comment 6 by tapted@chromium.org, Jan 19 2018

Owner: lgrey@chromium.org
Status: Assigned (was: Untriaged)
+lgrey could you take a look? - maybe this is actually  Issue 798739  which was fixed recently.

Comment 7 by lgrey@chromium.org, Jan 19 2018

Mergedinto: 777863
Status: Duplicate (was: Assigned)
Thanks, Trent!

Close, it's  Issue 777863  the "fix" for which caused 798739. Agree that the NSTrackingArea thing is a red herring but we should consider looking into suppressing or fixing that to reduce confusion/noise.

Sign in to add a comment