Memory Leak on export png????
ambassador at fourthworld.com
Mon Mar 19 09:56:53 CDT 2007
> Some more information on this.
> If I delete the Text counter object from the group that gets exported
> the it will output many more images (once it actually did all 500)
> before stopping. Doing this it will just continue forever, e.g. Most
> of the time I don't get the error dialog and mouseUp handler never
> I looked at the system activity monitor and found that 1.68 GB OUT of
> my 2 GB was allocated to RunRev, so I guess it really is leaking!
Is that physical memory or virtual? On OS X I've seen seemingly small
apps take up a surprising amount of virtual memory, but operate in a
much smaller physical space.
Although FWIW I've not seen my Rev usage climb that high while running
these tests. Are there plugins or other stacks running which may play a
> I also tried storing the image into a variable instead of a file and
> get the same problems.
> Not sure what else to try? Would be interesting to find out why it
> works on your system and not mine or Ian's. Anyone what to try this
> on their system? Haven't tried this at all under Windows.
> Thanks a lot and All the Best
>> Mac OS X 10.4.8, MacBook Pro 2.16GHz Core Duo, 2GB RAM
> Ok, are you using the standard RunRev IDE and not running anything
> other that the standard RunRev stuff?
I did the test both in Rev with only the default installaton, and in
MetaCard loaded up with several megs of my own tools. Same good result
> I set the fill color via the Property Inspector, not via a script,
> not sure if that would make a difference. I have removed all fill
> colors and I still get the error when writing file number 289. I've
> also tried making the object/rectangle smaller, still stops on file 289.
In theory it should make no difference, since the Inspector is setting
the same property I set in script. If anything, one might expect the
script to do a better job of exposing any issue with that since it's
working harder, setting the color over and over with each iteration.
Unfortunately this week I'm up to my gills in client work, so I won't be
able to run another test on this. It may be helpful to submit a test
stack which reproduces the problem reliably on your system to
support at runrev.com, so they can reproduce it there. With their
low-level debugging tools I'm sure that if they can reproduce it they'll
be able to fix it in short order.
Fourth World Media Corporation
Ambassador at FourthWorld.com http://www.FourthWorld.com
More information about the use-livecode