On 6. May 2012, at 17:11, Matteo Hausner wrote: >> So I assume that means the render clients are leaking. Most likely this is >> due to missing sync() on some objects. Try setting the 100 to 10 in >> Object::notifyNewHeadVersion and see who is throwing an assertion. > > After setting the value to 10, I'm getting an assertion on the root > node object, which I'm keeping in the FrameData. It looks like all the > previous versions are still kept alive until the assertion is thrown.
It means that you have a slave object which is behind calling sync() for more than ten versions. This typically happens if you forget to sync() your slave instances on the render clients, either because you're missing to traverse to the object or you've abandoned, but not unmapped and deleted the object. > For testing purpose I added the releaseObject() call. However I'm not > really sure if this is really needed, or if something else is missing > here... > I still seem to be somewhat lost... Is there anything else I have to > take care of before I map my new instances, or does Equalizer manage > everything by itself? If you've had a previous object which you are going to abandon, you have to unmap/release it. The design looks somewhat fishy, since you're recreating children objects when a child changes? I would expect this to happen only if the child itself is a different object. HTH, Stefan. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
