Port memory management and Image memory leak

Hi all,

I am using the Image object proposed in the Vision toolkit to share an image between my own Camera component and my own Display.
Listing the image addresses during execution, it seems to me that each time I set the grabbed image to the port, it destructs the previous image it contained to add the new one (resulting in cloning the image instead of copying it).

Then during execution, I don't really understand how my image data is managed by both components and the data port object.

Any clue on that?
Have people using the vision toolkit encountered some memory problems?

Thanks.

Charles

Port memory management and Image memory leak

The image port is a data port . It will save the last image until you give
it a new image.
If you define a buffer port, it will save the last image until some
connected port get it, then it will become empty.

2009/3/5 <charles [dot] lesire [..] ...>

> Hi all,
>
> I am using the Image object proposed in the Vision toolkit to share an
> image between my own Camera component and my own Display.
> Listing the image addresses during execution, it seems to me that each time
> I set the grabbed image to the port, it destructs the previous image it
> contained to add the new one (resulting in cloning the image instead of
> copying it).
>
> Then during execution, I don't really understand how my image data is
> managed by both components and the data port object.
>
> Any clue on that?
> Have people using the vision toolkit encountered some memory problems?
>
> Thanks.
>
> Charles
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>
>