Hi Maciej, I've just upped the notify messages in DatabasePager::capped_removeExpiredSubgraphs(..) and found out that it is pruning, but not quite in the way it should be, allowing number of PagedLOD to raise too far. It *used* to work, so I'm not sure what has gone amiss...
I'll will need to investigate this tomrrow as it's getting late here. In the meantime you'll need to set OSG_MAX_PAGEDLOD to 0 to get the old behaviour back. Robert. On Wed, Dec 17, 2008 at 7:36 PM, Robert Osfield <[email protected]> wrote: > HI Maciej, > > On Wed, Dec 17, 2008 at 7:09 PM, Maciej Krol <[email protected]> wrote: >> Now it makes sense, frankly I did not understand why You are trying do erase >> items from activePagedLODList rather than pagedLODList. It was beyond me, so >> just fixed bug locally. >> >> No crash in debug mode. Currently I am testing Your new pager with our paged >> databases. In old pager memory usage was contant about 80-100MB depending on >> scene complexity. In the new pager memory usage is contantly increasing >> reaching 500MB after 15 minutes of scene roaming. Setting OSG_MAX_PAGEDLOD >> to low value (i.e. 30) does not help. There no notify messages about >> releasing pages either. > > Is this growing memory consumption happening even with the fix? > > I don't see this issue with the databases I've tested so far. How was > this database built? > > Robert. > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
