Archived Beta Discussions > SlickEdit 2017 v22 Beta Discussion

VS2017-B1 Stop-build doesn't work for Java apps


Stop-build [Ctrl-C] is no good for Java apps, it just causes the JVM to produce a heap dump.  Stop-build needs to actually kill the Java process.
Try it out for yourself, compile and run this little demo.

--- Code: ---public class demo {
  public static void main(String args[]) {
    boolean machineRustedOut = false;
    while (!machineRustedOut) {
      try {
        System.out.println("Still here");
      } catch (InterruptedException ie) {
        System.out.println("Who interrupts my sleep?");
    System.out.println("Corrosion took its toll");   

--- End code ---

What you can do, is try to exit SlickEdit. It will attempt to exit the process buffer. When it fails, you should be prompted whether to kill the process. I think killing the process will work.

I sometimes just type "save-config" on the command line followed by "fexit". We've improved "fexit" to kill the process in the process buffer.

WARNING: "fexit" doesn't check whether buffers are saved. It just exits anyway. This command is more for the developers of SlickEdit. "safe-exit" is the safe way to exit SlickEdit.


[0] Message Index

Go to full version