Hi Valary, Don't use setImage from within your frame loop until you are switching between some fixed memory like the xine-lib plugin does.
It's better to update the data stored in the Image directly and call dirty, or to allocate the image memory separately and disable the deletion of the data on the image so the osg::Image(Stream) never calls delete on the data. Robert. On Fri, May 23, 2008 at 12:14 PM, Валерий Быков <[EMAIL PROTECTED]> wrote: > Ok, but there are next difficulty: I use function setImage for setting > new image in my thread, and this function deletes old image when it sets > new image. Therefore if updating thread updates image while main thread > updates texture then... segmentation fault. > In this case I must not to delete old Image for some time, but I don't > know how much time exactly. It depends on speed of copying image to > texture and on moment when texture starts updating... > > > > > _______________________________________________ > osg-users mailing list > email@example.com > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list firstname.lastname@example.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org