Hi Daniel,
Java has nothing to do with it. Unless you have a private cloud running Java, there's no Java anywhere (the personal edition runs on .NET exclusively). Service Studio always runs client-side, and is a native Windows program written in .NET, so there's no Java there either. Memory leaks are luckily mostly a thing of the past (on platform 6 for example, opening and closing a large eSpace would add 100s of MBs to the memory used by SS), so I don't think that's the case. The only thing I can think of is that your work station is really low on free memory when this happens. Have you checked via the Windows Task Manager what the memory status is when this happens?
Java has nothing to do with it. Unless you have a private cloud running Java, there's no Java anywhere (the personal edition runs on .NET exclusively). Service Studio always runs client-side, and is a native Windows program written in .NET, so there's no Java there either. Memory leaks are luckily mostly a thing of the past (on platform 6 for example, opening and closing a large eSpace would add 100s of MBs to the memory used by SS), so I don't think that's the case. The only thing I can think of is that your work station is really low on free memory when this happens. Have you checked via the Windows Task Manager what the memory status is when this happens?