Could not launch browser - process terminated on startup

[C. Howell]

I am trying out GWT for the first time this week and got pointed to SDBG when the Eclipse debugger refused to stop on breakpoints and some StackOverflow responses pointed me to this plugin.

I've installed the plugin and tried to follow the steps in the video at https://sdbg.github.io/

My menus differ slightly from the video, but I'm using:

• Ubuntu 16.04 LTS
  
• Eclipse Java EE IDE for Web Developers. Neon.2 Release (4.6.2)  20161208-0600
  
• GWT 2.7.0
  
• Google Suite Plugin 3.9.5v20160930-1755
  
• Chrome Version 55.0.2883.87 unknown (64-bit)
  

I'm working through the tutorial at http://www.gwtproject.org/doc/latest/tutorial/debug.html and have arrived at the "Debug" section.  So far everything is going smoothly.  Eclipse created for me a menu option "Debug As -> Web Application (GWT Super Dev Mode)" and that is what I am using to start up the app.  It compiles and functions as expected. 

I filled out an Eclipse Debug Configuration of type "Connect to Chrome" according to the example in the video, and when I start the Debug (with the button), the browser starts up on the home page and looks ready to go, but Eclipses pops up a window that says "Could not launch browser - process terminated on startup" and the application does not start up.

Any suggestions would be welcome.  I'd love to try out this debugger.

[C. Howell]

Sorry, I made a typo, I did not use "Connect to Chrome" but "Launch Chrome".  Perhaps I will try the other one.

[C. Howell]

Update:

If I kill allllll my Chrome processes, "Launch Chrome" still doesn't work, but, 

If I kill alllll my Chrome processes, create a "Connect to Chrome" Debug Configuration with basically the same inputs as I had for the "Launch Chrome" configuration, start a remote debuggable instance of Chrome from the command line with "google-chrome-stable --remote-debugging-port=9222" and then open http://127.0.0.1:8888, then I can debug my app.

[C. Howell]

By the way, if I try my "Connect to Chrome" debug configuration before I open the http://127.0.0.1:8888/StockWatch.html page in the instance of Chrome with remote debugging enabled, the debugger quits with a message that it can't find a tab with that page open.  I'm guessing this is intended behavior but probably helpful to know if you're trying it out.