Hi Yuan, I created a workaround for this problem on 22 Aug 2017 titled "reduce the need to reallocate the std::ostream buffer behind osg::Notify..." - link <https://github.com/openscenegraph/OpenSceneGraph/pull/314>: https://github.com/openscenegraph/OpenSceneGraph/pull/314
As it's only a few lines, I guess backporting to 3.2 will be rather simple. Regards, Laurens. On Wednesday, March 18, 2020 at 4:25:03 PM UTC+1, Yuan Cheng wrote: > > Hi Robert, > > thank you for the reply. You guess point me out to some way I could do > further problem analysis. > > 1.*could it be thread safety issue with the Windows iostream > implementation? - *that is a valid point I will check out this. > > * 2.SingleThreaded to see if it's related to threading - *I have tried > this, app does not crash as far as I have tested. > > * 3.disable the debug console output - *do you mean by disable this marco > DEBUG_MESSAGE? > I noticed a macro "OSG_NOTIFY_DISABLED" in include/osg/Notify. Shoud I > just define this in that file Notify? > > Best Regards > Yuan > > Am Mittwoch, 18. März 2020 15:28:51 UTC+1 schrieb Robert Osfield: >> >> Hi Yuan, >> >> I'm not a Windows users so can't comment on platform specifics, so have >> to take an guess, could it be thread safety issue with the Windows iostream >> implementation? >> >> Could you try with the Viewer threading set to SingleThreaded to see if >> it's related to threading. >> >> Could you also disable the debug console output to see if that addresses >> the problem? >> >> Robert. >> > -- You received this message because you are subscribed to the Google Groups "OpenSceneGraph Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osg-users/5856a1d6-3c29-4232-ac13-486e90d9b537%40googlegroups.com.
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
