HI Daniel, I'm afraid I don't have the time right now to look into this. It sounds like osgShadow will need to clean up the ViewDepedentData structures when a View/CullVisitor is deleted. I'd guess we'd need to introduce a local observer_ptr<> or osg::Obsever to catch when the CullVisitor gets deleted and then on the next frame clean up the appropriate data structures.
Robert. On 19 December 2012 14:38, Daniel Schmid <[email protected]>wrote: > Hi Robert, Wang Rui, and all > > I discovered a great gpu memory wasting in ViewDependentShadowMap. > > I use CompositeViewer with dynamically adding/removing view, and one > global scene graph for all views. > > ViewDependentShadowMap uses ViewDependentData to store the shadows etc. > These Data are stored in a map (ViewDependentDataMap) by CullVisitor. > > The problem is now, that for each new View that is added to > CompositeViewer, a new entry is stored in this map, which is never removed! > The removal scenario is not prepared at all. > > I can add/remove a couple of times a viewer, but then the GPU memory is > full and strange effects appear. > > Right now I have no solution for this. This issue is actutally a serious > problem for all view dependent data storage techniques. You have to make > sure that when a view is no longer used, all associated data is released > aswell!!! > > Thank you! > > Cheers, > Daniel > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=51636#51636 > > > > > > _______________________________________________ > 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
