NPE destroying Java3d component

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

NPE destroying Java3d component

ThomasR
Hi,

This happens infrequently and I believe I recall this from the pre-jogamp version 1.5.2 and earlier:

Error destroying java3d component
java.lang.NullPointerException
    at javax.media.j3d.NodeRetained.clearLive(NodeRetained.java:737)
    at javax.media.j3d.GroupRetained.clearLive(GroupRetained.java:2686)
    at javax.media.j3d.GroupRetained.clearLive(GroupRetained.java:2733)
    at javax.media.j3d.Locale.doRemoveBranchGraph(Locale.java:344)
    at javax.media.j3d.Locale.removeFromUniverse(Locale.java:313)
    at javax.media.j3d.VirtualUniverse.removeAllLocales(VirtualUniverse.java:358)

I'm using 1.6.0pre9

Of course, It's always easier growing a graph than paring it back.  I'm trying to plug memory leaks using Java3d

Any help appreciated, thank you to the developers and community contributors for keeping this alive.

Tom
Reply | Threaded
Open this post in threaded view
|

Re: NPE destroying Java3d component

gouessej
Administrator
Hi

Please use the very latest version (currently Java3D 1.6.0 pre 11) and provide a test case to reproduce this bug.

Edit.: We don't maintain Java3D 1.5.2 but your indication is helpful to know that it's not a regression of Java3D 1.6.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: NPE destroying Java3d component

ThomasR
Same problem with 1.6.0pre11 and jogl2.2.4  Looks like NodeRetained's VirtualUniverse reference is set to null before expected.  I guess the question is who has access to NodeRetainded.universe and can set it to null.  Just to be clear, I'm no longer using Java3D 1.5.2, but I do remember this Exception.