Posted by gouessej on Dec 14, 2013; 10:53pm
URL: https://forum.jogamp.org/java3d-memory-leak-with-threads-tp4030899p4030906.html

henry wrote

would using a more up to date version of java3d make any difference ?

You use a completely obsolete version whose maintenance had been stopped several years ago and which doesn't work on several recent operating systems. If you have any problem with this version, we won't be able to help you, no fix will be backported and anyway we don't build Java3D 1.5 anymore.

InteractiveMesh wrote

Give the latest version a try: http://jogamp.org/deployment/java3d/1.6.0-pre9/. Probably you will then be treated more politely here.

My article already contains the links to the latest JARs. I haven't been unpolite with him, using unmaintained pieces of softwares in production is very dangerous and this is typically the kind of things I want to avoid. I don't want to hurt anybody. We are some friendly members and we have to do our best to help the users of our APIs. Java3D 1.5 isn't maintained anymore, what can I do to help him as a first step instead of advising him to use our version? I'm not Oracle / Sun Microsystems, Java3D 1.5 is none of my concerns.

Edit.: Reminder: This section of the forum is entitled "JogAmp's Java3D Continuation" which means Java3D 1.6.x and later versions. Earlier versions are not maintained by JogAmp. If you want to get some help here, use our version, do it not to please me, do it because those earlier versions are unmaintained, you won't get any help on them and it would be completely nonsensical to expect any bug fix in Java3D versions that JogAmp is unable to build. Sorry to be unpolite enough to remind this.