Hi, On Wed, 2010-08-18 at 16:07 -0500, Carsten Neumann wrote: > Hello Gerrit, > > we are having one more problem with our app. The setup is like this: > > editor: > Aspect 0: multiple threads implementing the editor logic > Aspect 1: one thread sending changes to our cave > > cave: > Aspect 0: one thread rendering > Aspect 1: one thread receiving changes > > The cave part crashes under certain (reproducible) circumstances in > AttachmentContainer::resolveLinks on the unlinkParent call. It looks > like the attachment is already gone. > Looking through the ref counting for the attachments I've noticed that > there is the isMTLocal() check and depending on that a recorded or > unrecorded ref change is made. I don't think that is correct, since the > attachment map essentially behaves like a field and we never record the > ref count changes made by a field, so I believe these should all be > unrecorded. > Indeed the attached patch fixes our problem. What do you think? > The isMTLocal() change was done in r1357, maybe the commit message > "record attachment refcounts if container is a bundle to fix multi > aspect mem leak" allows you to recall what the problem addressed by it was?
short question, so I have the full picture, what was the reason behind r2472 because that one changed what was recorded and what was not ? kind regards gerrit ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
