Christiansen, Brad wrote:
Hi,
I am not sure if this is the same problem I came accorss many years ago when
we were developing our Java wrappers of OSG objects. We also has issues that
were caused by the finalizer deleting OSG peer objects from its own thread.
To get around the problem we simply changed the code in our finalize method
to simply queue the deletion opertion. This queue is then processed, and the
delete of the native osg object is done on our main update / render thread.
I'm pretty sure that's what's going on. Ideally I would like any thread
that takes control of the GL context to hold a lock until the context is
free, so that other code relying on it would work. However, I think
I'll probably go the route you suggest of queuing such actions onto the
main thread.
- Eron
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
