Hi, we just found and solved the most weird bug that was associated with our upgrade from OSG 3.2 to OSG 3.4 .
Our problem was that our batch programs (i.e. number-crunchers) would only run single threaded when launched from our application, but multi-threaded when launched on the command line. After 10 hours debugging, we found out that OSG 3.4 sets the CPU affinity from osgViewer::ViewerBase::startThreading(). When the process forks, this setting is inherited by the new process, and hence limits the new process to only run on one physical CPU. Our solution to this was to let the new processes unset the affinity mask, but I wish to make the community aware of this unwanted effect of OSG 3.4 Best regards, Kristofer Tingdahl -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: [email protected]:dgbes.com & opendtect.org *______________________________*
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
