Hi Andre, On 2/8/07, André Garneau <[EMAIL PROTECTED]> wrote:
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.
Curious. What happens when makeCurrent runs from the same thread? What happens on a relaseContext? As a general note I don't expect users to be stopping and starting threads too often in apps. The threading model handler in osgviewer.cpp is something that useful for experimentation but you won't find such a handler is most users apps, I expect them to start them app and only occasionally open and close windows. The but with this is that single thread multiple window usage forces the viewer to do lots of makeCurent, releaseContext pairs, so each frame we could be talking about pushing this issue. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
