APP quits in the mi...
 
Share:
Notifications
Clear all

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.

 

APP quits in the middle of the Integration when processing a large set

2 Posts
2 Users
0 Reactions
1,564 Views
(@jirestre)
Brown Dwarf
Joined: 7 years ago
Posts: 3
Topic starter  

I have used APP successfuly in other data sets, but this one 146 files is making APP quit unexpectedly without any warning. Same behaviour in MacOS Mojave 10.14.6 and Ubuntu 20.x. It just quits in the same spot about the 13 writing to the dataset (or something like that, in the first stage of the integration. There is enough HDD, more than 240GB of SSD and APP is given 24GB out of 32GB total system memory. 

Any ideas what this could be? I am attaching a file found on the APP application directory /Applications/AstroPixelProcessor.app/Contents/Java the heading of this file says that a fatal error has been detected in the JRE. I don't know if I should look for another log file. Just let me know. 

regards, 

Jorge

 



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Thanks for letting us know, could you test if this also happens with a smaller set of the same data?



   
ReplyQuote
Share: