#12 Problem with memory leeks when using image refs
I found a problem with putting image refs in the Data
Cluster of the data structures. Inside my Data Cluster I
placed 4 image refs. I acquired the 4 Images and stored
the reference to them in the Data Cluster. I found that
memory leeks were occurring. After tracking down the
problem I found that the flatten to string primitive used
the write case of the OpenGOOP Data Core.vi was
causing the problem. When I probed the string output of
the primitive the size was over 65000 characters.
Apparently image refs are flattened different than other
references. It seem like the image itself is converted to
a string and not its memory location.
I'm not sure if it was the image ref that caused the leeks
or the number of characters that had to be handled.
To fix the problem I had to go into the Object Data
Store.vi and convert the string to my Data cluster. This
Removes the need to flatten the cluster to get it into
the Data Store. This remove The leek disappeared and
performance improved.
The trouble with this solution is every time I change the
Data cluster I also have to change the "Data Store VI
Ref Type.vi" and every VI that used it.
Any other ideas or solutions would be greatly
appreciated.
Logged In: NO
I submited the bug I thought I was log on but I guess not.
Mballa@cherrycorp.com
Logged In: YES
user_id=1003366
I forgot to logon when I submited this bug.
Mark Balla
mballa@cherrycorp.com