Is this a JVM that Cursive started, or one that you started and connected with a remote REPL?

remote nrepl connection using "connect to server" with a local port forward

(local port forward meaning the connect to server connection is localhost and hard coded port)

In that case, I can’t think of anything that could cause Cursive to shut down the remote JVM - it doesn’t know anything at all about the process.

the port forward is to another machine, and the repl works correctly, but intermittently (1/10?) when i close the repl tab, the jvm on the other end shuts down

There must be something else going on, but I can’t imagine what it might be.

@U03A0EGF82E I had a similar problem with a Babashka nREPL, I don't know if this may be related to your problem. After I have produced a stack overflow, when I disconnected from the nREPL, that nREPL process crashed with a segfault. https://github.com/babashka/babashka/issues/1104

ah - mine was to a non-bb nrepl session

but interesting thing to try, anyway