Memory Leak on export png????

[Mark Smith]

On my machine it's showing Real:30-40 MB  VM:200-300 MB. It doesn't  
seem to change from beginning to end of the 1000 iterations...however  
many times I run it.

Rev 2.8.0, Mac 10.4.8, 1.5 Mhz G4 PB with 768 MB RAM. Standard Rev  
Studio installation with a few plugins loaded.

Mysterious.

Mark

On 20 Mar 2007, at 16:59, Dave wrote:

> Hi,
>
> I have got it working so I don't get the file name problem (giving  
> an error at file N) but it still leaks like there is no tomorrow. I  
> have tried doing the "x  = " trick as well as well as taking out  
> the counter field altogether and it still leaks. I can't get it to  
> work beyond 2000 images and that is at one quarter size, if I make  
> them full size then I will have no chance!
>
> I've tried this on Intel and PowerPC Under Tiger and Panther and I  
> get the leak on both machines and both versions of the OS.
>
> When you run the stack, do you have the system activity monitor  
> running? If so after 1000 images how much RAM is allocated to  
> RunRev (Real and Physical) ? For me:
>
> Real Memory    Virtual Memory
> 887.14 MB                1.25 GB                        1000 Images
> 1.68 GB                     2.07 GB                        2000 Images
>
> At this point the system becomes unusable and RunRev will either  
> quit itself or you will have to quit or force quit.
>
> Thanks a lot
> All the Best
> Dave
>
> On 20 Mar 2007, at 16:20, Mark Smith wrote:
>
>> Dave, as I said, it's now working as you would hope, and I can't  
>> reproduce the problem.
>>
>> Just out of interest, in view of what was happening here before,  
>> have you tried putting "x=" & x into fld "counter", rather than  
>> just x?
>>
>> Best,
>>
>> Mark
>>
>> On 20 Mar 2007, at 16:05, Dave wrote:
>>
>>> This is the kind of thing I was experiencing. I think there may  
>>> be two related problems, although one may cause the other. When I  
>>> tested it, it would run up to file 288 and not write file 289. I  
>>> then started it at file 289 and it would go wrong on the first file.
>>> e.g. change your loop to read like this:
>>>
>>> put   <WHATEVER>  into myStartOffset
>>> repeat with x =  (1 + myStartOffset) to (1000 + myStartOffset)
>>>
>>> and see what happens.
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your  
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution