At my end I do have the helgrind output that suggests a problem, but I don't have a crash, which makes it a bit more difficult for me to fully diagnose the problem and confirm a fix of the problem. The helgrind output is just a hint that somewhere in access of the ReadWriteMutex there is an issue, it doesn't actually pinpoint the actual failure mechanism.
Just my 2 eurocents: We were using openthreads to lock a crew of worker threads which were accessing a shared file cache locked with a mutex. We got a crash every once in a while. To check for the problem we changed the code to use tbb (thread building blocks). After that it did not crash anymore. It is too long ago to recall the details (not much of a help to nail it down either, sorry :), but I would agree to point my finger to core openthreads and not valgrind/helgrind/ osgparticle etc.
Stefan _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
