Out of Memory error running workflow with BreakPoint

[tomczak]

I'm getting an Out of Memory error in the middle of a fairly simple workflow on not that many, not that large images. It stalls PWP (I can't close the workflow execution box, nor the workflow window itself: "Operation in Progress: Complete image operation before closing window". What's a possible reason?

[den]

See: http://www.ncplus.net/~birchbay/tutoria ... /index.htm

Read the text starting with the word "Caution:..." just above the image comparison on/off example at the bottom of the web page.

Kiril may have a further update...

[ksinkel]

Please send me thet workflow and some sense of what size images your used.

Thank you,

Kiril

[tomczak]

Thanks,

The input files were actually quite large (about 20 images, 3x16bit Tiffs, ~60Mb each). WinXP32. I'll test it again and provide the workflow for testing, but I wonder what is actually happening - are input images accumulating in RAM somehow? Is it new to PWP6beta

mt

[ksinkel]

The workflow is careful to retain images only as long as they are needed and free them as soon as they are no longer required. Of course it is still possible to run out of memory. Memory is your RAM plus swap space, which is shared among all active processes. Because of this, turning off multitasking in workflow will lower memory requirements.

Running out of memory can cause an error in processing a particular image but should not crash the system, so I would like to get the workflow to try to reproduce your problem and see exactly where this is happening.

Kiril

[MikeG]

Removing images from my workflow doesn't release memory.
I'm running Windows 7 64bit Home Premium with 8GB of RAM.
Method.
Open workflow, load 4 tiff images and load 7 widget workflow.
The workflow shows 4 images 382.63MB
Using Windows Task Manager I can see memory in use shown at 1.78GB.
Run the workflow on all 4 images and memory in use rises to 3.99GB
From the workflow Opt button, choose "OK/Reject Marks", then "Remove all images"
The images disappear from the workflow but memory in use remains at 3.99GB
Close the workflow and memory in use returns to 1.78GB

From experience I know that I can process 10 images in this workflow before things really slow down. Then I have to close and reopen the workflow to continue.

Would be nice if "Remove all images" released memory.
If this is not feasible, would be nice if the workflow window size and position was remembered on closing a workflow.
Mike.

[ksinkel]

I am aware of this problem and will post a fix after testing is complete.

Kiril