Sergey,

The more I thought about this the more I doubted it may be related in your case, but I could not remove post already sent. However, we have found another, and this time looking much more real, PageLOD leak issue when node cache was active. Maybe this could be indirectly related to your case. In our case, cache keeping PageLOD ref counts above 1 was an additional factor that was neccessary for the leaks to happen, but I suspect that any other reference that would cause PagedLOD to not drop to 1 when when they were being disconnected from the graph may work as similar catalyst. I do not know exact details yet, my friend was investigating this issue and tomorrow we will post the report. You may want to check it. We will probably post it under the thread "PagedLOD experts ?" started few days ago (because, yes, "NeedToRemove" nodes are involved).

Wojtek

--------------------------------------------------
From: "sergey leontyev" <sleon...@ist.ucf.edu>
Sent: Wednesday, November 04, 2009 10:03 PM
To: <osg-users@lists.openscenegraph.org>
Subject: Re: [osg-users] Databasepager + multiple views + different camerapositions = memory leak?

Wojtek,
I tried what you suggested. Unfortunately it did not solve the problem :-(
Does this look like what you were referring to?

osg::ref_ptr<osgDB::ReaderWriter::Options> opt = new osgDB::ReaderWriter::Options;
opt->setObjectCacheHint(osgDB::ReaderWriter::Options::CACHE_NONE);
osgDB::Registry::instance()->setOptions(opt.get());
terrain = osgDB::readNodeFile(path);


thanks for the try anyways:-).

Sergey

------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=19196#19196





_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to