Cannot open APP tod...
 
Share:
Notifications
Clear all

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.

 

[Solved] Cannot open APP today. Stuck on 'Initializing OpenGL'.

23 Posts
3 Users
1 Reactions
2,058 Views
(@phrenos)
White Dwarf
Joined: 2 years ago
Posts: 9
Topic starter  

As the title says. I have a 2020 M1 Mac and Sonoma 14.1, running beta 26 of APP. 

APP has worked fine for months, but today it is stuck on 'Initializing OpenGL' at the splash screen forever, while the process is using 21% of the CPU doing... who knows what. 

I haven't made any changes to my Mac. 

Restarting the Mac does not fix it. 

 

EDIT by Mabula : solved with version 2.0.0-beta28


This topic was modified 2 years ago 2 times by B J RUSSELL
This topic was modified 2 years ago by Mabula-Admin

   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

Hello,

Same problem for me, since December 26. No installation, or any change.
I'm using the last release since a lots of weeks without problem.

MacBookPro 16' Intel + Sonoma
Restarting or reinstalling APP does not fix the problem.

Last step for me is : "application windows launched"

On my iMac 27'' Intel + Sonoma, everything is ok.

Error in the file attached

 

 
 

This post was modified 2 years ago 2 times by Régis RIGAL

   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

I've found a way to bypass the problem : 

If PixInSight is started, APP starts normally.

If PixInSight is not launched, APP don't start.

Strange...



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @phrenos & @prodalis,

Which Sonoma version are you running? Did the problem start after a macOS update perhaps?

Mabula



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

I'm using Sonoma version 14.2.1 (23C71).
I didn't notice the problem after an update, but with the bad weather I don't launch APP every day 🙂



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @prodalis,

Okay, thanks for the info, I will prioritize this issue for sure and will release a fixed version as soon as possible.

Mabula



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @prodalis & @phrenos,

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



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Posted by: @prodalis

Hello,

Same problem for me, since December 26. No installation, or any change.
I'm using the last release since a lots of weeks without problem.

MacBookPro 16' Intel + Sonoma
Restarting or reinstalling APP does not fix the problem.

Last step for me is : "application windows launched"

On my iMac 27'' Intel + Sonoma, everything is ok.

Error in the file attached

 

 
 

@prodalis

Thank you for the error report, the error which is thrown seems to be caused by our development platform, not by our code at first sight... I will check if there are known problems with our development platform and the latest macOS updates 😉

 

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @phrenos and @prodalis,

Can you try this test version 2.0.0-beta27-test ?

macOS Intel

https://appreleaseserver.s3.eu-central-1.amazonaws.com/2.0.0-beta27-test/AstroPixelProcessor-2.0.0-beta27-test-macOS-Intel-64-bit.zip

macOS Apple Silicon

https://appreleaseserver.s3.eu-central-1.amazonaws.com/2.0.0-beta27-test/AstroPixelProcessor-2.0.0-beta27-test-macOS-Apple-M-Silicon-64-bit.zip

and let me know if APP will start now on your mac ?

We have clear indications that the issue is caused by a bug in macOS Sonoma and this version has a workaround for it.

Thanks !

Mabula

 



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

Hello Mabula,

ERR.TXT :

WARNING: Unsupported JavaFX configuration: classes were loaded from 'unnamed module @3ecdb1d4'

 

OUT.TXT

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x00007ffb17518b8b, pid=3986, tid=81163

#

# JRE version: Java(TM) SE Runtime Environment Oracle GraalVM 21+35.1 (21.0+35) (build 21+35-jvmci-23.1-b15)

# Java VM: Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21+35.1 (21+35-jvmci-23.1-b15, mixed mode, tiered, jvmci, jvmci compiler, compressed class ptrs, g1 gc, bsd-amd64)

# Problematic frame:

# C  [AMDRadeonX6000MTLDriver+0x17cb8b]  void amdMtl_HWL_SetTexture<(AMDMtl_SqttMode)0>(GFX10_RenderCmdEncoderMembersRec*, unsigned int, id<MTLTexture>, unsigned int, unsigned int)+0x191

#

# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# /Applications/AstroPixelProcessor.app/Contents/Resources/hs_err_pid3986.log

#

# 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.

#

 

Thanks for your help



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

For me the problem is the same with the beta27 release.

Best regards

Régis



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

The error file generated with the beta27 release.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @prodalis,

Thank you, clearly, this error is in macOS Sonoma and not in APP's code, is there a way to revert the sonoma updates? I am not quite sure if apple even allows this ?

The error seems to indicate that Metal is still used as well... did you first uninstall the previous APP version before installing beta27? Metal should have been disabled.

Mabula


This post was modified 2 years ago by Mabula-Admin

   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @phrenos and @prodalis,

Okay, can you please try 2.0.0-beta27-test2 ?

macOS Intel

https://appreleaseserver.s3.eu-central-1.amazonaws.com/2.0.0-beta27-test2/AstroPixelProcessor-2.0.0-beta27-test2-macOS-Intel-64-bit.zip

macOS Apple Silicon

https://appreleaseserver.s3.eu-central-1.amazonaws.com/2.0.0-beta27-test2/AstroPixelProcessor-2.0.0-beta27-test2-macOS-Apple-M-Silicon-64-bit.zip

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



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

Hi Mabula,

with the beta27-test2 release, APP is starting !!

I hope it can help you !

Thanks for this debug and for all the work on APP ! 🙂 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

@prodalis Oh wow ! That is a bit unexpected, but I am glad I tried this !

Is the interface feel of APP the same as previously, I expect it is, but it is good to have more confirmation.

 

 



   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

I didn't notice any change.

I checked all menus, everything is the same visually.

Should I launch an integration task ?



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @prodalis,

If you did not notice any change visually on the interface, then all is okay for sure !

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.


This post was modified 2 years ago by Mabula-Admin

   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056

   
ReplyQuote
(@prodalis)
Brown Dwarf
Joined: 4 years ago
Posts: 9
 

Hi Mabula, no problem with the beta_28 ! Thanks !



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @prodalis,

Excellent, thank you very much for the feedback !

Mabula



   
ReplyQuote
(@phrenos)
White Dwarf
Joined: 2 years ago
Posts: 9
Topic starter  

Seemed to have started working again!



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi @phrenos,

That is awesome ! With beta28 for you? or perhaps with a new macOS update? Please be aware that the issue is caused by a broken metal framework in macOS Sonoma, and Apple will likely fix it in a newer update.

Mabula



   
ReplyQuote
Share: