Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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.
Just downloaded the latest version of APP. A message pops up that says APP unexpectedly quit and then asks if i want to send a report to Apple. I am running macOS Sierra version 10.12.6. Any thoughts as to why this would be happening?
Unfortunately we had to choose to move the earliest supported MacOS release to 11.0 which is the one after Sierra. APP 2.0 beta 13 is the last one still working on Sierra.
Hi @vincent-mod
I have the same symptom, but with the beta 26 and Sonoma 14.1.2
The day I installed it, everything worked, but some days later and since I've had the same message as described by James. I uninstalled and reinstalled APP. I tried the beta 25 again, then came back to the beta 26, but nothing helped... Maybe an issue with the last Mac OS update?
Jean-Marc
I have also had this problem on my Mac Pro running Ventura 13.4.1 yesterday and today. Restarted the computer, reinstalled Beta 26, reinstalled Beta 25, and get similar error message.
I am running MacOS Ventura 13.4 and the same problem happened to me. The pop-up message says Java quit unexpectedly. Can anyone help?
I updated my MacBook Pro to Sonoma 14.2.1 and still get the same problem with JAVA crashing. Are their any solutions?
I installed the Beta 13 version and it works. What has changed?
Hi @jmd67650 @casejim @mephy-liu,
Thank you all for sharing this issue. I will investigate this on my mac computers, 2 days ago on Saturday, all was okay still with APP on my mac computers with macOS Sonoma, but i did not install the latest macOS updates, maybe there is an issue now with one of those latest updates ?
Can you try to run APP from a terminal and check if there is some error message when starting APP?
Mabula
Hi @mabula-admin
I don't know if this is the right procedure, but here's what I did:
I opened /Applications/AstroPixelProcessor.app/Contents/MacOS/ and double-clicked on universalJavaApplicationStub
The response was:
Error: VM option 'UseJVMCICompiler' is experimental and must be enabled via -XX:+UnlockExperimentalVMOptions.
Error: The unlock option must precede 'UseJVMCICompiler'.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I tried opening Beta 26 again and it now works as expected.
Hi @mabula-admin
New status:
One hour ago, I updated MacOSX, I'm now in sonoma 14.2.1
I've updated Java to 21.0.1 (12.29)
I have uninstalled and reinstalled beta 26
Now, if I run the command java -jar astropixelprocessor-2.0.0-beta26.jar, it works (which was not the case before)
But if I double-click on the APP icon in LaunchPad, I get the message "AstroPixelProcessor has quit unexpectedly".
For information, I've been using APP on this Mac since 2020.
Hi @jmd67650 and @casejim and @mephy-liu,
Can you try the following for me:
Open a terminal window and cd to the Applications folder with command
cd /Applications
Then run APP with the following command:
open -a AstroPixelProcessor.app -o out.txt --stderr err.txt
If the application won't start again, kill this process
Then check the contents of both out.txt and err.txt files which were created.
You can see the contents with the cat command like:
cat err.txt
Can you share what is shown in both the out.txt and err.txt files?
Thanks,
Mabula
I installed the Beta 13 version and it works. What has changed?
Hi Jim, many things have changed, but 2 critical parts can explain the issue I think. We changed our graphical OpenGL dependency, it was updated in beta14. Since beta13, we have upgraded our development platform as well several times... currently, with beta26, we use the latest version of our development platform Oracle GraalVM JDK 21.0.1+12.1, maybe there is an issue in the development platform with the latest macOS update. I am still investigating 😉
Mabula
Hi @mabula-admin
I don't know if this is the right procedure, but here's what I did:
I opened /Applications/AstroPixelProcessor.app/Contents/MacOS/ and double-clicked on universalJavaApplicationStub
The response was:
Error: VM option 'UseJVMCICompiler' is experimental and must be enabled via -XX:+UnlockExperimentalVMOptions.
Error: The unlock option must precede 'UseJVMCICompiler'.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Hi @jmd67650,
Thanks for trying, I should have given better instructions 😉 please try this :
Open a terminal window and cd to the Applications folder with command
cd /Applications
Then run APP with the following command:
open -a AstroPixelProcessor.app -o out.txt --stderr err.txt
If the application won't start again, kill this process
Then check the contents of both out.txt and err.txt files which were created.
You can see the contents with the cat command like:
cat err.txt
Can you share what is shown in both the out.txt and err.txt files?
We run APP with GraalVM which needs special VM args provided in AstroPixelProcessor.app, so by opening with the open command and directing application output to some txt files the application will run exactly the same as intended.
Hi @mabula-admin
New status:
One hour ago, I updated MacOSX, I'm now in sonoma 14.2.1
I've updated Java to 21.0.1 (12.29)
I have uninstalled and reinstalled beta 26
Now, if I run the command java -jar astropixelprocessor-2.0.0-beta26.jar, it works (which was not the case before)
But if I double-click on the APP icon in LaunchPad, I get the message "AstroPixelProcessor has quit unexpectedly".
For information, I've been using APP on this Mac since 2020.
Thanks @jmd67650 for the update.
The java that you install has no bearing in how APP should works or runs, because we install APP together with a version of java together with special VM arguments. In this manner, we can fully control APP and the user does not need to concern him-/herself with installing a certain java version.
If you run APP with
java -jar astropixelprocessor-2.0.0-beta26.jar
it will run with your java version, but we can not offer support for that. APP is not supposed to be started like that and it will not work as intended.
Only when you start APP with the following instructions, you can start it correctly from the terminal in the way it is supposed to start:
Open a terminal window and cd to the Applications folder with command
cd /Applications
Then run APP with the following command:
open -a AstroPixelProcessor.app -o out.txt --stderr err.txt
If the application won't start again, kill this process
Then check the contents of both out.txt and err.txt files which were created.
You can see the contents with the cat command like:
cat err.txt
Can you share what is shown in both the out.txt and err.txt files?
I updating my iMac Pro Intel to Sonoma 14.2.1 now and will report back if I run into the same issue or not 😉
EDIT by mabula: I have updated my iMac Pro Intel to Sonoma 14.2.1 but everything is fine still, I am not running into problem, so it's vital that you send me the output from running it from the terminal with
open -a AstroPixelProcessor.app -o out.txt --stderr err.txt
Thanks
Mabula
I don’t know of anything that was updated on my side that cleared the problem. I will check the update history and see if anything updated in the background. Thanks!
Following your last recommendation, here is the result.
The content of err.txt:
janv. 11, 2024 6:21:22 AM com.sun.javafx.application.PlatformImpl startup
WARNING: Unsupported JavaFX configuration: classes were loaded from 'unnamed module @27b3a2ec'
Assertion failed: (cmdBufInfo->device == rsrc->_res.device), function amdMtlBronzeCmdBufUpdateRsrc, file amd_mtl_bronze_hw_cmd_buffer.c, line 1126.
and out.txt is empty.
Thanks.
Jean-Marc
Hi @jmd67650, thank you very much !
The third line is unexpected and must be the cause of the issue:
Assertion failed: (cmdBufInfo->device == rsrc->_res.device), function amdMtlBronzeCmdBufUpdateRsrc, file amd_mtl_bronze_hw_cmd_buffer.c, line 1126.
The other 2 lines are normal behaviour and no problem.
Now I need to find out what is causing this error.
Can you tell me a bit more about your mac computer on which this happens? Which mac model is it and what graphical hardware is inside? It looks like it is an AMD graphical chip?
Mabula
Hi @jmd67650, the error seems to indicate that the issue is in fact in the macOS metal code... caused by the latest macOS updates I would think, since earlier all was working.
APP's interface is rendered using metal at the moment, but I can make a test version where this is disabled to see if that solves the issue. I will provide a download link with the test version later today to see if that explains the issue and solves it for now 😉
Mabula
Hi all @jmd67650 @casejim @mephy-liu
Some related searches on Google related to the error output
Assertion failed: (cmdBufInfo->device == rsrc->_res.device), function amdMtlBronzeCmdBufUpdateRsrc, file amd_mtl_bronze_hw_cmd_buffer.c, line 1126.
reveal that macOS Sonoma seems to have several bugs inside related to their Metal API unfortunately. Many java based applications using metal for interface rendering don't seem to work on Sonoma and do work when metal is not used. All these applications worked on macOS versions before Sonoma with metal enabled.
The good news, is that we can build APP with metal disabled, which I will do today and I will share a test version later today for you to test if all is okay then 😉
Mabula
Hi @jmd67650 @casejim & @mephy-liu
Can you try this test version 2.0.0-beta27-test ?
macOS Intel
macOS Apple Silicon
and let me know if APP will start now on your mac ?
This test version has metal disabled for interface rendering of APP because we have clear indications that macOS Sonoma has a bug in the metal API code somewhere...
Thanks,
Mabula
@mabula-admin
Unfortunately, I got the same message:
janv. 11, 2024 1:45:27 PM com.sun.javafx.application.PlatformImpl startup
WARNING: Unsupported JavaFX configuration: classes were loaded from 'unnamed module @5713f060'
Assertion failed: (cmdBufInfo->device == rsrc->_res.device), function amdMtlBronzeCmdBufUpdateRsrc, file amd_mtl_bronze_hw_cmd_buffer.c, line 1126.
I uninstalled beta 26 and installed beta 27. Nothing, except once the APP started. But I never managed to restart it again.
My Mac is MacBook Pro 2018
Processor 2,9 GHz Intel Core i9 6 cœurs
Graphic card Intel UHD Graphics 630 1536 Mo
macOS Sonoma 4.2.1 (23C71)
Jean-Marc
Hi @jmd67650,
Thank you very much, okay we need to try something else then... I will let you know when another test version is available.
Hi @jmd67650, @casejim & @mephy-liu
Okay, can you please try 2.0.0-beta27-test2 ?
macOS Intel
macOS Apple Silicon
I am not sure if this beta2 will do the trick, but it might. If it does not, we will continue digging deeper into this issue.
Please share the exact error again that you get if it fails, thanks.
Mabula
@mabula-admin
It's working now! Well done!
Many thanks for the quick fix.
Jean-Marc
Hi @jmd67650, that is awesome ! Thank you very much for testing so quickly 🙂
I will release an official beta27 tomorrow with this fix, got confirmation that it was solved for another user as well in a different topic.