Hi Robert, >> Sounds a bit odd, the osgViewer's threading should be decoupled entirely from the driver, the only thing it'll know about things is that their are makeCurrent() and >> releaseContext() being called, unless everytime there is makeCurrent() isn't kicking off a thread. >> Are you able to track all the threads running on the machine? How certain can you be of their origin? Is there anything we can do to help identication of which threads >> are going awol?
The thread spawned for the driver implementation resides in the osgViewer process (sorry if I was not clear). It is spawned when the first makeCurrent() call is made on a rendering context. I tried getting rid of this thread yesterday by deleting context, etc. but it only seem to go away at process termination. I will do some more investigation on this this evening, but it could turn out to be an NVIDIA issue. André _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
