Hi Romain, I have just done a code review of OSG master and the 3.4 branch and spotted a fix to the osg::State destructor that avoids deleting the GLExtensions object when there still other graphics contexts using it. I have merged and checked in this osg::State destructor fix into the OpenSceneGraph-3.4 branch.
Could you try out the OpenSceneGraph-3.4 branch or master and let us know if this resolved the bug for you. Robert. On 25 July 2017 at 14:23, Romain Roch <[email protected]> wrote: > Hi, > > We recently upgraded our application to OSG 3.4.0 and we are now getting a > crash when deleting an osg::View instance. > > Our application creates an additional view using a shared context with the > main view. This view is displayed in a separated Qt dialog. > The crash occurred when this second view is deleted: the destruction of > its osg::State deletes the GLExtensions instance associated to the context > id. > The current VBOs that were initialized will make the application crash as > soon as they are used since their internal GLExtensions instance is dead. > > Is it a known limitation of OSG with MDI applications, i.e. one cannot > delete a view that shares a context while the main view remains active ? > > Would it be possible to add a test that check whether the graphics context > is shared in osg::State destructor before deleting the associated > GLExtensions instance ? > > Cheers, > Romain > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=71313#71313 > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
