Quick question for those of you who may know -- if you have an <extremely common for users to exit JMP this way, thus pretty much always bypassing all <
Has anyone seen this / aware of any work-arounds?
The main problem I'm running into is that I have JMP launch an event-loop Python script and attach the executable to a window, then I communicate to Python via localhost sockets. The window close script will terminate the Python session gracefully and such. When JMP is closed in the manner above, this doesn't happen and JMP then freezes, but the JMP windows are all gone -- so JMP remains in the Task Manager list with its full set of resources (often more than 1GB) and will only be killed by manually ending the task.
Since the RunProgram result must be tied to an active JMP window (for event-loop purposes I suppose), and since the window gets forcibly closed in the manner I describe above, the RunProgram variable gets destroyed before I'm able to properly shut down Python.
It's a mess and one for which I wish had a solution, but as of yet I'm not seeing it.
