By default, when a client application crashes, the SSM will automatically close the connection to that client and all of the sessions that were active on that connection will be aborted.
You can modify the default behaviour by setting abortSessionIfClientDisconnect="false" in the SessionTypes > Type section of the application profile. In the case of a client crash, this will allow your session to remain open, and your workload will continue to run.
Your session will be "orphaned" in the SSM, taking up system resources, until you do one of the following: