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 tested beta41 regarding the error in https://www.astropixelprocessor.com/community/main-forum/beta40-problem-error-warning-when-using-lnc/#post-34155.
The integration of the 460 lights was performed flawless with LNC 1st degree, 3 iterations and Bayer drizzle 1x, 0.85 droplet 🙂
BUT 🙁
Since in the 460 lights there are some lights that are not so good, I thoght it would be a good idea to integrate just 75%, which are 345 lights. So I dont restart the programm after finishing the 460 lights but set the slider "lights to stack" to 75% and startet integration. Integration started, and after about 3 lights a SUDDEN CRASH happens 🙁
Hi @juergenn,
That sounds like a very other type of crash, more like instability with hardware or even the software layer between the OS and our development platform. Maybe you can run in the following way to produce an error log that should help us:
Windows and MacOS:
or Linux:
Try to reproduce the error and send me that log file, hopefully I can pinpoint the cause of the crash then. If you can not reproduce the crash, or if it happens more randomly (not at the exact same moment in processing), it will be very likely instability on you system, in that cause you need to check the ram modules and possible overclock settings.
Let me know if this helps.
Mabula
Hi Mabula,
I just restartet APP and set the 75% from the beginning. Now I'm at light 100 of 345 and it seem to work now. Since its still running I will tra again first 100% directly following 75% hoping the crash happens again. I will try to use your commands you mentioned above.
Hi,
I did the test and rerun APP, starting with 100% of the lights, then 75%. Now all went fine 🙂
What I'm wondering is that when closing APP the following message appears (but until closing APP all went ok):
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f5c3aac054b, pid=3655, tid=3813
#
# JRE version: Java(TM) SE Runtime Environment (25.0.2+10) (build 25.0.2+10-LTS-69)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0.2+10-LTS-69, mixed mode, tiered, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C 0x00007f5c94102eb8
#
# Core dump will be written. Default location: Core dumps may be processed with "/bin/false" (or dumping to /opt/AstroPixelProcessor/core.3655)
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid3655.log
Thanks for fixing the beta40 issue so fast 🙂
P.S:: I'm running Opensuse 15.6.
I installed it via RPM
Okay thanks @juergenn,
Can you send me that /tmp/hs_err_pid3655.log file if you still have it, can you send it to support@astropixelprocessor.com ?
I will have a good look at it, it could be something related still to incompatibility with Linux Wayland or OpenSuse perhaps. Is your linux installation using Wayland?
Next release, we will again move to a newer platform, JDK26, it should again enhance performance and give better compatibility with the new Linux versions.
Mabula
