Hi David, There were various changes to osg::Notify during the 3.1.x dev cycle. Could you try out OSG-3.2 and see how you get on.
Robert. On 2 August 2013 22:54, David Fries <da...@fries.net> wrote: > I spent a few days tracking down a crash I was having generally when a > terrapage terrain was paging. This is using OSG 3.1, when I finally > caught the corruption I found that both the DatabasePager thread and > the Draw thread were calling OSG_NOTIFY. > > I wrote up a test that does little more than start up a bunch of > threads and print messages and found it too crashes. I am testing on > both Linux x86-64 gcc 4.7.2, and Windows 7 Visual Studio 10 and both > crash, though it crashes much quicker on Windows. > > It will crash pretty quickly with the default (no arguments) on Windows. > > The following arguments are working for me to crash on Linux on a 12 > core (24 with hyperthreading), x86-64 system. > ./ThreadedNotify 48 10000000 2 2 > > It has been pointed out that cout/cerr are thread safe, so it should > be possible to make osg::notify thread safe as well. In this program > it helps when I reduce the notification level, at least with the low > number of messages being printed it seems to be unlikely. > > -- > David Fries <da...@fries.net> PGP pub CB1EE8F0 > http://fries.net/~david/ > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
