Kill process without killing JMPJMP does an amazing job of chugging along so even long analyses get done eventually (unless there are hardware limitations). However, sometimes these long processes are kicked off on accident or without realizing how long they will actually take.
I would like to suggest a way to kill the current process so the single thing I started stops, but I don't have to force close all of JMP and lose any other work I have going on. I know myself, and many colleagues, have done these things - from an accidental click to a botched while loop - so a way to save JMP from this 'killer process' would be greatly appreciated!
Content OrganizationData AccessSharing and Communicating ResultsRe: Kill process without killing JMPI wouldn't say Esc is the death sentence for all stuck code, but it's definitely the first thing to try.
Personally, I've never had any of my stuck code killed by the esc key :frowning_face:
Re: Kill process without killing JMP
so
Esc
the death sentence for all stuck JSL codes?
Re: Kill process without killing JMPTry pressing Esc
Re: Kill process without killing JMPIs
for(i=1,i<10,i--,print(i))
really the death sentence for all unsaved data tables?
No chance to stop it?
Re: Kill process without killing JMP@Jonas_Rinne
Re: Kill process without killing JMP@Sarah-Sylvestre This is great news, thanks!
Re: Kill process without killing JMP - Status changed to: Investigating@nathan-clark - Thank you for this suggestion, it has been submitted and is being evaluated for possible inclusion in a future release.
Re: Kill process without killing JMP@PatrickGiuliano, it certainly is a tall order, but it would be so great 
Saving the session script is a great idea though, I'll have to start doing that!
Re: Kill process without killing JMPYea this one is likely a tall order? It would be really really nice though! This must be happening to practically every seasoned JMP user.
The best way for me to not lose work is by saving a Session Script intermittently throughout my session:

I then open and run the saved .JSL script after JMP crashes and viola! I'm back where I left off....
Otherwise the Autosave Timeout is supposedly a good option (File > Preferences > General; see below), but it doesn't really work for me even if I set it to some reasonably short interval such as 2 or 5 minutes.

Re: Kill process without killing JMPIt would be quite nice if JMP were multi-threaded with an exposed event loop and exposed signals/slots. Probably won't happen any time soon though...
Re: Kill process without killing JMPhate to kill JMP completely when I run mixed models that take hours to run, often have unsaved work (table edits) that is then lost.
Re: Kill process without killing JMPSomehow related to the submitted wish request -Of if not, perhaps it could be considered as an independent wish request
Sometimes an expensive analysis may be kicked off (intentionally or not) that the user may not prefer to wait to completion.
A way to simply return an estimated time to completion : XXX mins .. confirm ? .. could give the user the extra option to launch the analysis or not.
Re: Kill process without killing JMP@altug_bayram that's a nice idea 
a somehow related idea:
define a timeout for platforms in the preferences: Timeout
Re: Kill process without killing JMPAt the moment, I see these 3 types of processes where we need a way to kill them:
- JSL code:
use ESC - Column Formulas:
is there a way to stop all evaluations?
- JMP platforms
which need hours to get finished
a) Speed up Tables/Update
b) life distribution (TS-00122043)
...
or maybe just because of the huge input data
are there additional cases?
Concerning 1-3:
#1 : ESC
#2 could be fixed, if there was an official way to stop all column formula evaluations?
#3 could be fixed easily, either via a cancel button in a platform window which is created as a separate Task - or via Timeout
@Sarah-Sylvestre @ can you give an outlook for JMP 18.1
... or a feedback about the current status of the investigations?
Re: Kill process without killing JMP - Status changed to: AcknowledgedRe: Kill process without killing JMPI would love this.
My current approach is to accept that if my JMP is so bogged down it crashes, it's a sign I need to take a break.
But the option to kill the evaluation process would be great.