saa...@sf... wrote:
> Hi Travis
>
> Not sure if you've had a chance to look at the previous code I sent or not,
> but I was able to reduce the code (see below) to its smallest size and still
> have the problem, albeit at a slower rate. The problem appears to come from
> changing values in the array. Does this create another reference to the
> array, which can't be released? If this problem does not have a work-around
> or "fix", please let me know.
>
This is now fixed in SVN.
-Travis
|
