UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Astro Pixel Processor 2.0.0-beta44 release notes
- FIXED NEW MEMORY CONTROLS / FASTER AND MORE STABLE ON BIG DATASETS
We have further improved the new internal memory controls. APP should have lower latency now and should no longer stall/pause/freeze while processing big datasets. This fix should ensure that it works on all computers now.
To make APP run faster and more stable on big datasets, the new memory controls can no longer fragment the internal memory of APP. That caused the slowing down of APP in older versions. Latency of the application has improved as well. When APP starts now, it will report how much memory it can use safely without compromising the stability of the Operating System. It reports the maximum memory and also a soft maximum memory value. While processing, the soft maximum memory should not be crossed unless APP really needs the memory for a very intensive memory task after which it can never cross the maximum memory threshold. After any task, APP should also gradually release the used memory again back to the Operating System. On computers with little RAM memory (less than 16GB of RAM), the soft maximum and maximum will almost be equal or equal. On systems with plenty of RAM (more than 64GB of RAM), the soft maximum will be fixed at 32GB of RAM which should ensure fast and stable processing without consuming too much memory which can slow things down.
This is a further improvement over the below release note from beta43, this change and improvement should now work on all computers.
- IMPROVED INTERNAL MEMORY CONTROLS / FASTER AND MORE STABLE ON BIG DATASETS
As reported here : https://www.astropixelprocessor.com/community/main-forum/randomly-stopping-freezing-during-integrations/#post-34236 APP could stall/slow down or even freeze when processing big to very big datasets (500+ frames). The lastest APP releases have many code optimizations making it quite a bit faster, but the memory clean up internally was not able to keep up with all the GigaBytes of data that were processed. The old memory controls internally were fragmentating the memory causing these instability issues now and more quickly as well. Luckily, we are able to prevent this fragmentation completely by using a very different memory configuration internally. Technically, we have switched APP from using java's default G1 garbage collector with many G1 tweaks to using the more advanced Z garbage collector. This proves to be much better for data throughput and stability. Processing big datasets should not slow down APP at all anymore after having done several 100s of frames in integration.
