Hi,

sorry for the late reply, just back in office and trying to catch
up with things ;-(

On Wed, 2005-05-11 at 14:28 -0500, Dirk Reiners wrote:
>       Hi Johan,
> 
> On Wed, 2005-05-11 at 18:24 +0200, Johan Grafstrom wrote:
> > Hi!
> > 
> > Thanks for your quick reply and sorry for the delayed reply on your 
> > reply. We have been busy removing a few other bugs from our application.
> 
> As long as they're bugs in your app and not in OpenSG I'm not
> worried. ;)
> 
> > The problem with the doubled memory consumption remains though. We made 
> > a short test program to provoke the behavior, based on the multithread 
> > example in the Tutorial. The program is attached to this mail.
> 
> Thanks for the example, I could reproduce the effect. You're right, it
> actually makes a copy.
> 
> Gerrit, looking at it the problem is that void MField<FieldTypeT,
> fieldNameSpace>::setValues(const Self &obj); is called instead of void
> MField<FieldTypeT, fieldNameSpace>::setValues(const StorageTypeParent
> &value); as void MField<FieldTypeT, fieldNameSpace>::syncWith(Self
> &source); just calls setValues(source);. 
> 
> Is that on purpose? Can you fix that? Does that still happen in your new
> FC code?

will have a look at it. For the new version it is not completely done,
still have to finish all the wishes regarding sharing mfield data with
external data pools (Johannes and my own wish list ;-)). But before I
still want to finish my valgrind runs on the new version.


regards,
  gerrit




-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to