Bug #142

when we close JTorX before animation servers have started, these servers are not cleaned up

Added by Axel Belinfante over 11 years ago. Updated over 11 years ago.

Status:ClosedStart date:24 Jun 2009
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:1.1.0

Description

When we start JTorX on the windows terminal server, where it takes 'forever' to get anidot and animsc servers started, and then exit JTorX before these servers are fully up and running, they are not killed but continue to run.

unfortunately, so far we do not have a good solution to this.

TODO: test whether this is also an issue on faster (ordinary) windows machines.

Question: can we detect this issue (i.e. that the user wants to close, but we are not ready to be closed yet), and if so, delay closing the main JTorX app (gui) until we can really close everything?
Of course, it would be rather annoying not to be able to close the JTorX window immediately -- but maybe that is less annoying than leaving spurious processes around -- especially if this mainly (only) happens at the windows terminal server.

History

#1 Updated by Axel Belinfante over 11 years ago

  • Status changed from New to Closed
  • Target version set to 1.1.0
  • % Done changed from 0 to 100

solved the problem, essentially by closing the stdin of the animation programs.
in addition, we try to invoke the destroyer that we register to clean up when we stop the java program,
but this is not always helpful: it does not yet do anything useful while the process is still being launched,
and the launching phase may take quite a while on our windows terminal server (or so it seems).

fixed in commits 36082d3a0e3793cb5ce8715fef4706d13d8f379c and d679102f6beaf4ef2602dc9f274ef8d4c324efb7

Also available in: Atom PDF