UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8872.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.105 Safari/537.36

Steps to reproduce the problem:
1. Open the Secure Shell app as a Window
2. Create a connection that includes the SSH port forwarding argument, i.e. something like "-L 8888:localhost:8888"
3. Start the connection.
4. Hit "Ctrl-Shift-N" to create a new Secure Shell Window
5. Attempt to start a new session with the connection again.

What is the expected behavior?
Some kind of error message on the second window indicating the port is not available.

What went wrong?
The second window just sits there without connecting or giving any indication of what is happening.

WebStore page: https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo

Did this work before? N/A 

Chrome version: 55.0.2883.105  Channel: stable
OS Version: 8872.76.0
Flash Version: Shockwave Flash 24.0 r0

Using ssh at the command line in Linux you will get an error message "bind: Address already in use" in this case, then proceeds to create the SSH session without the port forwarding.