Releasing Memory and Virtual Memory
userevolution at dreamscapesoftware.com
Tue Aug 11 22:42:44 EDT 2009
My apologies to everyone for wasting your time...
My script is setup so images that can be exported by Revolution (JPEG,
GIF, PNG and Paint) are done so by Revolution, and all other image
formats are exported using the EnhancedQT External.
The variable holding the destination file type info was incorrect,
resulting in my if-then comparisons always skipping the built-in
Revolution exporting, and utilizing the EnhancedQT External.
This constant usage of EnhancedQT for converting and exporting 100+
images would result in the memory buildup. It now seems that this
problem is resolved, but I still have to figure out a way of getting
EnhancedQT to release it's hold on my memory.
But all in all, I know that all of the suggestions that everyone gave
have allowed me to optimize my script to make it run even faster than it
Thanks to everyone that helped with this. I really appreciate it.
Compress your photos quickly and easily with JPEGCompress 2.9!
Derek Bump wrote:
> Well, I tried everyone's suggestions except 1, the use of "send in x
> seconds" method. All of the other suggestions resulted in no
> improvement in RAM usage... which sucks because they were all pretty
> easy to implement.
> So with a big thank you to all who chimed in, and my fingers crossed,
> I'm going to rewrite the script to incorporate the suggested message
> sending. Hopefully that will provide the solution I'm looking for.
> Derek Bump
> Dreamscape Software
> Compress your photos quickly and easily with JPEGCompress 2.9!
> Scott Rossi wrote:
>> Recently, Derek Bump 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.
>> Three things I would try:
>> - try setting the filename of the target image, as opposed to using "put
>> - save the stack each time after exporting 10 to 20 images or so
>> - if saving every so often doesn't do anything, try deleting the image
>> object, and creating a brand new one, and saving, as opposed to putting
>> empty into the existing image
>> Hope one of these helps.
>> Scott Rossi
>> Creative Director
>> Tactile Media, Multimedia & Design
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode