On 20 Mar 2007, at 14:14, Richard Gaskin wrote:

Dave wrote:
Yet more information, I tried running it under 2.6.6.152 (using the older screen rectangle command syntax) and I got it to export 2000 image files. It ran a *lot* slower but it didn't leak memory, so the problem must have been introduced in version 2.7.x.

FWIW, last night I experienced crashes in one of my apps built with v2.8 that has never crashes before. This app is different from most others I work on mainly because of the number and frequency of file-writing operations. There may be a connection to what you're seeing, or something else. If I find a pattern I'll get back to you.

I can't see that this could have been tested past a cursory glance before releasing it.

While RunRev has had a history of some of the shorted Beta cycles I've ever seen, in this case the time between v2.6 and the current v2.8 spans more than a year and during most of that time this issue eluded a recipe. That this is being seen now and a recipe is being honed in on is a good thing, but I'd hate to see RunRev err too far the other direction with Beta cycles extending longer than a year. Some bugs are not immediately evident, and will take time to discover amidst the nearly infinite combination of tokens that can be executed.

All I know is that if I were to write something like this (a file/ image data exporter) then once I'd got it working past the the point where I could write an image file in all the different formats then I'd run a soak test on it and let it run for *loads* of (like 10,000 +) of iterations and I would have checked that memory was being released. In fact I wrote an external command module that does something similar (it analyzes movie frames) and I *did* soak test it and I *did* find memory leaks.

For me, this is software engineering 101.

All the Best
Dave


_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to