Can you provide a crash ID or crash report?

@rsesek : Unable to provide crash ID as it is not generated.

This needs a crash report to proceed. Please look in the Crashpad/completed directory.

The assigned owner "yfulgaonkar@etouch.net" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

yfulgaonkar@etouch.net, is it still happening?

Adding Internals>Installer. Is "Start Google Chrome" button doing anything special?

With response to comment #6

Able to reproduce above issue in Mac(10.12, 10.11.6, 10.12.1) OS on latest canary #58.0.3028.0 build using the steps given in comment #0. Kindly review an attached screen cast.

Note : The crash id is not generated.

Thank you.

Deleted: Actual_tab_crash.mov 11.0 MB

Actual_tab_crash.mov 11.0 MB Download

Removing the Blink>Loader label, as this is an installer-specific issue.

To be clear:

- Start Chrome anew
- From the Welcome dialog, click the "Learn More" link. A window will open but the page will not load.
- Click the "Start Chrome" button
- The tab opened with the "learn more" link will sad-tab.

"(Unable to narrow down the range using tool as the above issue is not reproducible on chromium builds, hence providing the suspect from change log)"

Per-revision bisects are on official builds. Can we get a per-revision bisect?

With response to comment #12,

Retried bisecting, but can not run Per-revision bisect since the Mac revisions are not supported. Hence assigning an issue from change log info :
Change log URL : 
https://chromium.googlesource.com/chromium/src/+log/52.0.2722.0..52.0.2723.0?pretty=fuller&n=10000

Suspecting : r 390983 ? from CL

@brucedawson  : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Unable to provide Per-revision bisects as the regression range revisions are not supported by per revision on Mac OS.
Thank You.

It is unlikely (probably impossible) that my change could be causing this. Unfortunately, without bisect information or a crash dump it is impossible to guess what the culprit change might be.

Assigning to an OSX developer in hopes that they can reproduce the crash under a debugger or otherwise get a crash dump in order to figure out what is going on. Or, assign it to another OSX developer who can do that.

On Windows I would recommend attaching windbg or Visual Studio before the tab crashes in order to catch the crash. I'm not sure what the equivalent tools are on OSX.

It seems extremely unlikely this is a regression caused by brucedawson@'s change. Per my conversation with ellyjones@ about a related bug (Issue 700314), I'm guessing the problem is that the Chrome application has not really launched, and so clicking the link cannot succeed. It seems strange that this ever worked.

Looking at the change log for first_run_dialog.mm, I'm wondering if this change (from the same general timeframe) might be the cause:

https://chromium.googlesource.com/chromium/src/+/2df4a9ef0a0abb0c21d8994fe597c68f6637d95d