[osg-users] Heap Corruption

[Bruno Oliveira]

Another possibility is that your code is allocating and deallocating memory
in separate module DLLs. However, in Windows, each DLL has separate memory
spaces and that cannot be done.

You should check if that's the case by any reason (e.g. creating a
osg::ref_ptr in a dll of your own and allowing osg::ref_ptr to be
deallocaed automatically by another dll module).
This is solved by providing proper deallocators.

2017-01-10 12:04 GMT+00:00 Voerman, L. <l.voerman at rug.nl>:

> Hi Théo,
> I think you basically found out that the osg notify system is not thread
> safe, the call to osg::Notify from
> osg130-osgUtild.dll!osgUtil::CullVisitor::apply(osg::Drawable & drawable)
> Line 1036    C++
>     OSG_NOTICE<<"CullVisitor::apply(Geode&) detected NaN,"....
> is probably running in parallel with a different thread calling
> osg::Notify as well while triggering a resize of the buffer (too).
> Setting OSG_NOTIFY_LEVEL=WARN will probably avoid this crash.
>
> Regards, Laurens.
>
> On Tue, Jan 10, 2017 at 12:39 PM, Alberto Luaces <aluaces at udc.es> wrote:
>
>> Ok, the next I would do is to see what is OSG trying to print in this
>> stack frame (the ninth from the beginning):
>>
>>      osg130-osgUtild.dll!std::operator<<<std::char_traits<char>
>> >(std::basic_ostream<char,std::char_traits<char> > & _Ostr, const char *
>> _Val) Line 806    C++
>>
>> maybe that could serve as a hint...
>>
>> --
>> Alberto
>>
>> _______________________________________________
>> osg-users mailing list
>> osg-users at lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
>
>
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20170110/8707d2e9/attachment-0003.htm>