June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Hi Mabula,
I’ve been testing APP 2.0 latest release on a new system and wanted to report a consistent issue.
System:
- Windows 11
- i7-11850H (16 threads)
- 64GB RAM
- RTX A4000 laptop GPU
Dataset:
- ~400 light frames
- 16-bit, ~49MB each
Behaviour:
- 2.0.0-beta41 (Oracle JDK 25.0.2)
→ crashes during integration and drizzle (javaw.exe faults) - 2.0.0-beta38 (GraalVM 24)
→ same dataset completes integration and drizzle successfully
Notes:
- No issues on older laptop (32GB RAM) with earlier 2.0 builds
- Reducing threads did not prevent crashes in beta41
- Beta38 runs stable even with 10 threads
It seems related to the newer Java runtime / memory handling in beta41.
Happy to provide logs if useful.
Thanks for all your work on APP.
kind regards
Bryan
P.s. had some help from AI solving this problem and when I asked if I should report my findings back to you it strongly recommended this and composed the above message 😊
Hi @astr0dude,
Thank you very much for the clear report, indeed. javaw.exe is the problem then, so the issue is not in our code but in the development platform somehow related to windows 11.
I can make a test version in the coming days with a different development version and or different memory handling to see if that solves it. Can you test if i send you a new test version based on the upcoming beta42?
Mabula
I would be more than happy to help and test the upcoming version
kind regards
Bryan
Great Bryan @astr0dude,
I will probably release beta42 in the coming days with adjustments for the development platform and memory usage and will then let you know once available, if that has the same issue, we will need to dive deeper into this or go back to an older version of the development platform.
I will keep you updated.
Mabula
Hi Bryan @astr0dude,
I have prepared a test version for 2.0.0-beta42 with modifications that possibly fix this crash. I have created a test version for Windows.
You can download it here:
This version includes additional improvements as stated in the release notes for beta42:
Can you test beta42test1 and let me know if this has solved the issue or not?
Thanks,
Mabula
Hi Mabula,
Thanks very much for the test build.
I’ve completed a full integration run using the new version (2.0.0-beta42test1, Oracle JDK 26.0.1) and can confirm it completed successfully without any crashes.
This is the same dataset and workflow that was consistently failing before:
- ~400 light frames (~49MB each, 16-bit)
- Multi-night dataset (several sessions)
- Multi-channel processing
- Drizzle enabled
- LNC enabled (1st degree, 2 iterations)
- 12 CPU threads
- OpenGL4 enabled
Previously (beta41 / JDK 25), the application would crash during the LNC/integration phase. With this test version, the entire process completed cleanly.
Observations:
- CPU usage stable (~60–80%) throughout integration
- RAM usage remained well controlled (~15–23GB used, no runaway allocation)
- Multiple LNC passes and filter transitions completed without issue
- Final integration completed successfully
This appears to have resolved the instability I was experiencing under heavy real-world processing conditions.
Thanks again for the quick response and fix — happy to run further tests if needed.
kindest regards and many thanks
Bryan 😊
Hi Brian @astr0dude,
That is really great ! Thank you very much for testing and the detailed feedback.
Volkan @volkanovun in the other related topic also confirms the crashes are gone now. There must have been a problem in JDK25 which is fixed in JDK26.0.1. I also think that I know what the issue was from the issue tracker of the JDK.
I will go ahead and finish work on beta42 and will release it later today 😉
Edit, you can find beta42 with the fix in the downloads section.
Mabula
beta42 working well!
Thank you Mabula
Kind regards
Bryan
Hi @astr0dude & @volkanovun,
And please give beta43 a spin as well. It should be faster and more stable/robust with big datasets !
I will probabluy make another adjustment with new memory controls today, so 2.0.0-beta44 might be in the downloads section when you check, please try that then.
Mabula
Great Volkan @volkanovun and @astr0dude, thanks for the feedback !
This morning I released 2.0.0-beta44 which has additional configuration for the new internal memory controls that beta43 has. It should be even better configured for all systems now. It should run fast, stable and continuously. Latency of the application should be better as well when compared to beta42 and earlier.
Mabula
I will download and test at my earliest opportunity
thanks Mabula
I am currently trying to create a simple program that will detect subs with satellite trails in and send them to a new location for review as I often still see faint trails even after using sigma rejection, adaptive rejection etc especially if I am aggressively stretching for flux
kind regards
Bryan
Hi @astr0dude,
Okay, let me know your findings. I assume that you adjust the outlier rejection settings? Lowering the high kappa would still show the satellite trails? Maybe you can send me the problematic data so I can see and solve this ?
Mabula
Pleased to report back Beta-44 is working well and is definitely faster at processing my data
I need to experiment with the outlier rejection settings for sure.
Having progressed (over the last couple of decades) from dslr to ccd, which required 20min subs to cmos which now results in so many more subs to process, and resulting in multiple larger file sizes that challenged my older laptops processing capabilities, not to mention star-link, which has been both annoying and exciting as an independent dish installer it has been frustrating processing data or blinking though hundreds of subs to try and eliminate the trails
Beta-44 and my new laptop will hopefully help with this, but it was a fun distraction using Ai tools to try and create a python based program that would quickly scan my subs and separate suspect subs with satellite trails
it works ok, 17th iteration of the program, but as a result of just a couple of days "playing" I have a new understanding and respect for talented astronomy software program developers such as yourself
Thank you for your hard work
Kind regards
Bryan
Hi @astr0dude,
Great, thank you very much for your feedback 😉
Yesterday I released 2.0.0-beta45, please give it a spin, you can find it in the downloads section. I have made more improvements and optimizations, you can read about that in the release notes. It has further tuning of the internal memory controls, speed should be good and memory control must be again better as with beta44.
Mabula