out of scope Memory Allocation Issue in PixInsight

[fernandoyang]

System Configuration​

• Processor: AMD Ryzen 9 9950X
• RAM: Previously 4x48GB (192GB total), currently 1x48GB
• Operating System: Ubuntu 24.04
• PixInsight Version: 1.9.3

Issue Description​

After hardware configuration changes, PixInsight seems unable to properly recognize the decrease in available memory:

1. With the original hardware configuration (192GB RAM), PixInsight ran WBPP scripts normally, with memory usage reaching 160GB+
2. Due to a motherboard issue, only 1 stick of 48GB RAM can currently be used
3. In the new configuration, PixInsight crashes with Out of Memory (OOM) errors when running the same WBPP tasks
4. After increasing system swap space to 128GB, PixInsight completes processing but swap usage reaches up to 100GB and obviusly, takes much much more time to finish the process
5. Tried re-run "performance -x" command in console, the issue was not resolved

Suspected Cause​

The application doesn't appear to properly detect system memory changes and still attempts to allocate memory according to the previous configuration, leading to OOM errors after memory reduction.

 

[cloudbait]

System Configuration​

• Processor: AMD Ryzen 9 9950X
• RAM: Previously 4x48GB (192GB total), currently 1x48GB
• Operating System: Ubuntu 24.04
• PixInsight Version: 1.9.3

Issue Description​

After hardware configuration changes, PixInsight seems unable to properly recognize the decrease in available memory:

1. With the original hardware configuration (192GB RAM), PixInsight ran WBPP scripts normally, with memory usage reaching 160GB+
2. Due to a motherboard issue, only 1 stick of 48GB RAM can currently be used
3. In the new configuration, PixInsight crashes with Out of Memory (OOM) errors when running the same WBPP tasks
4. After increasing system swap space to 128GB, PixInsight completes processing but swap usage reaches up to 100GB and obviusly, takes much much more time to finish the process
5. Tried re-run "performance -x" command in console, the issue was not resolved

Suspected Cause​

The application doesn't appear to properly detect system memory changes and still attempts to allocate memory according to the previous configuration, leading to OOM errors after memory reduction.

I don't think PI stores any information about memory (which is supported by examining the config file). It seems more likely to me that the problem is with your system, either not handling a single memory stick properly or a bios configuration problem such that more memory is being reported than is actually available. (The performance command assesses efficient thread usage, nothing to do with memory.)