Releasing Memory and Virtual Memory

[Phil Davis]

In ancient times I used the hasMemory() function to force garbage 
collection and free up memory. But maybe it only worked that way in 
SuperCard... can anyone comment on its effectiveness in Revolution?

Phil Davis


BNig wrote:
> Derek,
>
> do you import the 100 or so images in a repeat loop?
> If so try whether adding a wait 2 milliseconds in the repeat loop helps.
> Or alternatively try to do it in a "send" structure. In my experience Rev
> has problems releasing memory in a repeat loop. When I changed to a "send to
> me in 2 milliseconds" no more problem with memory build-up.
> regards
> Bernd
>
>
> Derek Bump - Dreamscape Software wrote:
>   
>> Is there any way to force Revolution to "let go" or "release" excessive
>> amounts of memory?
>>
>> I've got a project that scans through a folder of images, imports the
>> image into an image object (via put url "binfile:"), exports it as a
>> JPEG, then puts "empty" into the image object (to free it up).
>>
>> The problem is that after 100 or so images, the amount of memory that
>> Revolution is using is over 1.5 GB's of Real RAM and 3 GB's of Virtual
>> RAM.  This, of course, slows down all of my other applications until I
>> close Revolution.
>>
>> Meanwhile, in the same project, I can do the same thing manually with
>> just 1 image, and the memory goes back down.  I import the image into an
>> image object, export it, and put "empty" into the object.  When I do so,
>> the Activity Monitor shows a 10 MB drop in RAM usage.
>>
>> Any help is greatly appreciated!
>>
>>
>> Derek Bump
>>
>>     
>
>   

-- 
Phil Davis

PDS Labs
Professional Software Development
http://pdslabs.net