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.
I just installed the beta43 on my linux PC (opensuse 15.6). It seem to work, but didnt done further tests til now. When starting APP with gtk-launch the following warning occurs on startup:
[0.003s][warning][gc] ** WARNING! INCORRECT SYSTEM CONFIGURATION DETECTED! **
[0.003s][warning][gc] The system limit on number of memory mappings per process might be too low for the given
[0.003s][warning][gc] max Java heap size (115856M). Please adjust /proc/sys/vm/max_map_count to allow for at
[0.003s][warning][gc] least 208540 mappings (current limit is 65530). Continuing execution with the current
[0.003s][warning][gc] limit could lead to a premature OutOfMemoryError being thrown, due to failure to map memory.
I'm just curious what that means? I'm using a Ryzen 5900X with 128GB Memory.
Hi @juergenn,
Thank you very much for reporting this. Did beta43 run fine despite that warning?
Beta43 uses a different internal memory configuration, this warning is definitely related to that. I will do some testing on my linux systems. Maybe I need to further adjust the new configuration to remove that warning.
I do think that APP 2.0.0-beta43 will run fine despite the warning. Did it? Or did you get an Out Of Memory issue?
Mabula
i tried a set of 460 lights, two sessions, different focal length. Bayer drizzle 1.5, droplet 1.0. LNC 1st degree, 3 iterations.
At the start again the warning, but it worked fine, no problems.
I started it with gtk-launch, after closing APP I get the following message:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb)
Hi @juergenn,
Please update to 2.0.0-beta44 and let me know if those warnings are gone. I think it should be fixed with the adjustments for beta44 😉
How much RAM memory is in your Linux system?
Mabula
Hi Mabula,
i have 128GB of RAM. I run same project with 460 lights again. The warning is still there and also an error report file (I started with gtk-launch again). i attach both files (I had to rename the .log-file to .txt).
But the program run without problems, despite error/warnings.
Regards
Jürgen
Hi @juergenn,
Today, I have released 2.0.0-beta45. Can you test this and let me know if all is okay? Are the warnings still there or not?
You can find beta45 in the downloads section.
Mabula
Hi Mabula,
I testet Beta45 with the same set of files: everything is working ok and no more warnings 🙂
