Hello,
first of all, excuse my bad English !
I'm experiencing a problem with memory management within Pixinsight version v1.8.4 on a Win7 64bit machine.
When using the batch debayer script (or using the debayer process on an image container) on many (~6000) images the system runs out of memory. Watching the task manager I can watch free memory continiously fading down until there is no memory left and then Windows freezing. When I stop batch debayering before this is going to happen, close and restart Pixinsight memory then there is free memory again but not all (15gb less then on a fresh system boot and YES -- I waited until Pixinsight is completely shut down as can be seen in the task manager under 'processes'). So the only conclusion for me is to permanently take care that there is a little memory left, do a reboot and then continue. I don't think it is a good idea to limit the assigned memory by changing memory in bcedit (Windows) and I don't know any other methods to limit the memory assigned to a program within Windows 7.
So, I have two questions about it:
Is that behaviour changed in Pixinsight version v1.85 ?
What can I do about it? I think there is a problem that Pixinsight does not really close an opened image after doing debayer and so memory use is growing.
The machine itself is running very stable. I'm on Win7 Pro SP1 x64, 32gb RAM, i7 2600 CPU, enough SSD space (3 disks), swap file is set to always 32gb.
Any help would be helpful
Hannes
