Rubymine debug session crashing with vagrant ubuntu on windows 10

I'm running RubyMine 2017.3 on Win10, virtualbox vagrant with ubuntu.  When I'm running the server (debug mode), periodically the server will crash.  This happens annoyningly often and seems to be driven moodiness of rubymine or vagrant or something.  I wont see it for weeks, then I'll see it every 30 min or so.  

In the rubymine console window I will see:

Process finished with exit code -1

The next client web browser access will fail with "empty response from server", and subsequent requests will get connection refused.

Doing a ps -ef | grep ruby will show a zombie ruby-debug-ide process, which I must kill (otherwise restarting rubymine debug will show server already running)

Once that's done, I can restart the server from rubymine and after the painfully long server startup, I'm going again.  But it's really annoying.

Logs and Info

My vagrant file is here:

the only unusual thing is I have an explicit private network. (

Rubymine logs are below.  Not sure what's causing the 'processWillTerminate', but it's having problems with remote port forwarding removal.  FWIW I dont really need the remote port forwarding as I am using an explict private network to connect via browser to my app.  If there is a way to dsable RPF, and that's the problem, LMK)

Rubymine logs show the following

2017-12-30 00:08:13,652 [198983224] INFO - emote.RubyRemoteProcessHandler - processWillTerminate: removing port forwarding - Port forwarding[from remote server to local localhost:3000]
2017-12-30 00:08:13,652 [198983224] INFO - emote.RubyRemoteProcessHandler - Unable to remove port forwarding
com.intellij.remote.RemoteSdkException: Failed to delete local port forwarding
at com.intellij.ssh.process.SshProcess.removeLocalTunnel(
at org.jetbrains.plugins.ruby.remote.RubyRemoteProcessHandler.removeTunnels(
at org.jetbrains.plugins.ruby.remote.RubyRemoteProcessHandler.access$000(
at org.jetbrains.plugins.ruby.remote.RubyRemoteProcessHandler$1.processWillTerminate(
at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at com.intellij.execution.process.ProcessHandler$5.invoke(
at com.sun.proxy.$Proxy17.processWillTerminate(Unknown Source)
at com.intellij.execution.process.ProcessHandler.fireProcessWillTerminate(
at com.intellij.execution.process.ProcessHandler.access$200(
at com.intellij.execution.process.ProcessHandler$
at com.intellij.execution.process.ProcessHandler$TasksRunner.execute(
at com.intellij.execution.process.ProcessHandler.notifyTerminated(
at com.intellij.execution.process.ProcessHandler.notifyProcessTerminated(
at com.intellij.remote.BaseRemoteProcessHandler.onOSProcessTerminated(
at com.intellij.remote.BaseRemoteProcessHandler$1.a(
at com.intellij.execution.process.ProcessWaitFor$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: com.intellij.ssh.SshTransportException: Failed to delete local port forwarding
at com.intellij.ssh.SshSession.removeLocalTunnel(SshSession.kt:66)
at com.intellij.ssh.process.SshProcess.removeLocalTunnel(
... 22 more


Hello Josh,

sorry for the delay. Just to be sure, how have you added the remote SDK? Via Vagrant configuration or via SSH? Do you manage to run the app (not to debug)?



It is a vagrant remote sdk.

The failure is intermittent while it is running.  Starting it always works.  It will run for a while, and then have the crash.

The app itself will run just find on the linux command line with rails s

I'm not sure if the problem occurs when running not debugging in rubymine.


Hello Josh,

I've trie running debug with Vagrant based ruby SDK (in my case it was ubuntu/trusty64 box, rvm, ruby 2.4.1) on Windows 7 and it worked fine. I didn't manage to set up SDK with your box because it cannot be found. Does it crash on all the Rails applications or only a certain one? Are there any steps for stable reproduce?


Im using ruby 2.3.1, my box isnt published but it is based on trusty64

I have two rails apps on the box, and ive mostly seen it with the bigger of the two.(much bigger)

Lately Ive been just running the app from the command line, rails s...., to avoid the problem,

Ill switch back to running it debug in rubymine and see if i can narrow it down

What do those error messages in the logs surrounding the failure actually mean?  What causes them?

that would be helpful in narrowing it


Please sign in to leave a comment.