All Java3D threads set to daemon

Bug 1111 - Java3D does not dispose correctly after use

Note there is a strong possibility that this could have side effects
particularly in headless environments.

However a daemon nature is more correct and will allow applications to
exit gracefully and when expected.

In testing normal swing operations can cause non-exiting.
E.g. 
JFrame f = new JFrame();
f.pack();

will not exit unless 
f.dispose(); 
is called. This is unrelated to Java3D.

0 files changed, 0 insertions, 0 deletions