Hi Jannik, I have merged your first set of changes to BufferObject, but not the ones to Texture related calls. The later have a cache of ref_ptr<TextureObject> that remains in scope during the Texture::apply() methods so there shouldn't be the same issue with BufferObjects getting deleted. If you have a specific case that shows a problem with TextureObject management let me know and I can look at it. Want I want to avoid is unneccesary ref()/unref()'s happening on TextureObjects on every Texture::apply() like you had.
BufferObject changes now merged and submitted to svn/trunk. Robert. On 7 May 2015 at 18:03, Jannik Heller <[email protected]> wrote: > I just noticed the TextureObject code (TextureObjectSet being a mostly > identical copy of BufferObjectSet) has the same problem. Updated the patch to > fix that too. And I added a comment to the generateTextureObject / > generateGLBufferObject functions warning about the multithreading hazards. > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=63658#63658 > > > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
