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

Steps to reproduce the problem:
1. About 20+ steps getting angular cli setup in eclipse
2. Start angular cli server - wait
3. Debug application in chrome
4. Chrome starts, then exits.
5. Eclipse reports -
Failed to get tabs for debugging
Connection refused (Connection refused)

What is the expected behavior?
The ideal behavior would be to have local dev version of the web site appear in a new session under a new tab. But this has never worked.

Before updating to 64.0.3282.140 the behavior was identical - except - chrome didn't exit. On the second and following attempts the tab was created.

What went wrong?
My suspicion is that Eclipse/Angular CLI is requesting a tab before Chrome is in the appropriate state. In the previous version (unknown rev) Chrome tolerated this error and remained open allowing Eclipse to make a second attempt. Now, Chrome shuts down or crashes creating a user triggered loop.

Did this work before? Yes Unknown

Chrome version: 64.0.3282.140  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

I'm going to try and work backwards installing previous versions until I get it working again. Hopefully you find a fix before I do.

Thanks