Robert, I want to take us back to a bug that was found in Sep. of 2008.
http://www.mail-archive.com/[email protected]/msg15483. html I do agree that there was an issue at this point not having some kind of locking system in place when accessing the parents, but is a global mutex the right answer when _OSG_REFERENCED_USE_ATOMIC_OPERATIONS is defined. If two unrelated group nodes on different threads add unrelated children, there is the possibility that one will block the other. A perfect example of this is the main thread and a database pager. As stated by the previous thread, this is not only related to group nodes. Drawables, Nodes, StateAttributes, and StateSets also use the global mutex. Was there a reason for using a global mutex instead of a mutex owned by an instance of osg::Referenced? Ryan H. Kawicki The Boeing Company Training Systems & Services Software Engineer _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
