Hi Vincent, The OSG threads that will run automatically are the DatabasePager when you have paged databases and any viewer threads. There is a viewer method for getting the threads.
However, the threads are designed to be arbitrarily paused, you can start and stop the viewer threads via Viewer::startThreading/stopThreading() but this creates and destroys threads so not quite what you are after. However, I'm kinda perplexed how you think you might be "managing memory" more efficiently by pausing threads and "doing stuff" and then un pausing. I can't help but feel that you need to take a step back and work out what you mean by managing memory efficiently, there are lots of different ways of doing this, but given no information about what you mean and you actual motivation for this others like myself can't really point you in the right direction, the best I can say is from the sound of it you are currently looking in the wrong place. Robert. On Thu, Jan 13, 2011 at 8:14 AM, Vincent Bourdier <[email protected]> wrote: > Hi all, > > Currently working on a way to manage the memory efficiently, I would like to > know what are the osg threads running ? > > I mean there are some threads in the databasePager, depending on the > rendering threading mode there are threads for the render, the cull, or > whatever... > > Did I miss something important ? > What are the osg threads ? > > I would like to be able to make some king of "pause" on all treads to be > able to allocate the whole available memory for the process without having > some crash because a thread would be working (and so allocating memory) > during this operation. > > Thanks for your help. > > Regards, > Vincent. > _______________________________________________ > 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
