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.
I run APP (2.0.0-Beta36) on a Windows 11 PC. Historically I Remote Desktop (RDP) into this machine to use APP and check on progress bars. Starting at or around Beta35, when I RDP into the machine the running instance of APP seems to have crashed. I'm having trouble consistently reproducing the issue, but it has happened during various stages of processing, and more frequently in the last month or so. Other open programs are still running, only APP seems to have failed. Has anyone seen this issue?
I rarely seem to get a log file when this happens, the few I see point to a JRE crash.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffa761bdf1, pid=27520, tid=11780
#
# JRE version: Java(TM) SE Runtime Environment Oracle GraalVM 23.0.2+7.1 (23.0.2+7) (build 23.0.2+7-jvmci-b01)
# Java VM: Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 23.0.2+7.1 (23.0.2+7-jvmci-b01, mixed mode, tiered, jvmci, jvmci compiler, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C [awt.dll+0xdbdf1]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Hi Jonathan, @merkwood
Thank you very much for reporting this. The error occurs in awt.dll which indeed is part of Oracle Java. awt is actually part of the graphical user interface, so the crash seems to be related to graphical drawing of the application some how. If the issue always occurs at the same moment in processing, it could be a real bug in the java runtime. But if the biug is rather random and would not always happens, it could indicate a hardware instability on the computer on which APP is run that you connect to by RDP. Since APP is tough on hardware resources, it can crash with an instable system when other applications would still "survive" sort of speak.
Can you make sure that the system is stable? Is it not overclocked? Possibly do a ram test?
Finally, you can try to run APP from the commandline in the following way. Open a commandline (with administrator priviliges if installed for all users).
Go to APP's installation directory which will be:
C:\Program Files\AstroPixelProcessor
or
C:\Users\[yourOSusername]\AppData\Local\Programs\AstroPixelProcessor
and execute APP with the following command:
AstroPixelProcessor.exe > log.txt 2>&1
After the APP crash or after closing APP, all system out and errors should be stored in the log.txt file. Please check the contents of the log.txt and let us know if the crash happens again.
Thanks,
Mabula
I also was using RDP to control my processing/stacking PC today when APP crashed. I thought maybe GPU acceleration may have been the culprit so I changed the OpenGL setting to CPU, still crashed without error.
So I am not the crazy one ... 🙂 I have the exact same issue with beta 39, the crash comes on step 6/Integrate always, but I am using TeamViewer. I will try to generate a log tomorrow. As I can see, the problems come with multi-night projects, single night projects does not crash.Â
