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.
Hi all,
Getting a reproducible hard crash in beta41 on my Sony A7 IV .ARW files. JVM aborts and the window just disappears. Wanted to flag it here in addition to the email I sent to support (with the .ips files attached).
Setup: macOS 26.4.1, Apple Silicon (MacBook Pro 18,3), APP 2.0.0-beta41 on GraalVM 24.0.1+9.1. Shot on Sony A7 IV, 14-bit ARW, ISO 8000, 4 s subs. 51 lights / 15 darks / 16 flats of comet C/2025 R3 (PanSTARRS).
What I've tried:
- Full set (lights + darks + flats), defaults on 2) CALIBRATE → "create Masters & assign to Lights" → crash every time, 5-10 s in.
- Lights-only (no darks/flats). Got past master generation / assign a couple of times, but then crashed at 3) ANALYSE STARS instead. Same signature.
- RAM slider at default (512 MB) and at max — same crash either way, so it doesn't look memory-related.
- Cmd+Q and relaunch between attempts.
Crash signature (from the .ips):
- Exception Type: EXC_BAD_ACCESS (SIGABRT)
- Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000008188
- Triggered by Thread 75 (Java: pool-91-thread-1)
- Crashing frame:
arm_libRawConverter.jnilib Java_com_ariesproductions_rawConversion_LibRawConverter_getRawData + 344
The crash is in the native raw decoder (getRawData), and the fact that it also crashes at analyse-stars with lights-only lines up — star analysis re-reads each light through the same decoder. Looks like a null-pointer deref at a small struct offset (0x8188), which feels like a header/metadata parsing issue specific to these ARWs.
Anyone else seeing this? Happy to send sample .ARWs if it helps repro.
Thanks, Gwen
Hi Gwen @gwencruise,
Thank you very much for sharing the issue with us.
The camera model Sony A7 IV with ARW files was fully tested in APP some time ago already. Today, I have tested all of our ARW test files from this model on my Apple M4 macbook Pro and all was fine, no crashes.
Can you check if perhaps some of the frames are corrupt somehow? Did you see in the Console Panel on which frame it crashes? Your description seems to indicate that the files are recognized fine and initially a couple will load after which a crash occurs on a particular arw file.
Please upload a small batch of ARW files that will produce the error so I can test it and find the issue and also avoid APP crashing on this in the future.
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder with your name and issue like : Gwen-SonyARW-issue
And upload the files there and please let me know once done, i will look at it as soon as possible.
Thanks,
Mabula
