Share:
Notifications
Clear all

Black Friday & Cyber Monday Sales on Renter's & Owner's licenses - sale will end on the 1st of December 2020 at 12:00 UTC

16 November 2020 - Wouter van Reeven has officially joined the Astro Pixel Processor Team as a moderator on our forum, welcome Wouter 🙂 !

31 July 2020 - Comet Registration video tutorial using APP 1.083-beta1 released.

30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.

9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp

2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!

[Sticky] I can't adjust APP's memory with the CFG button ! It's always the same when I start APP...  

  RSS

(@mabula-admin)
Quasar Admin
Joined: 4 years ago
Posts: 2476
February 27, 2019 17:27  

Hi all,

Astro Pixel Processor is an Oracle JAVA application and the startup parameters of JAVA to run APP properly are configured in the APP installation files. You should never have to alter these yourself.

However, some other application builders have the bad habit of asking the user to set JAVA startup parameters on the Operating System level.  This is not good.

This means that all Java applications on your operating system, will only be able to run with the settings that are set on the Operating System level, because they will overrule the settings on application level.

So which operating system level envrionment variable is concerned here? It's the variable

_JAVA_OPTIONS

with argument -XmxXXXXM or -XmxXG

The XXXXM could be 1024M, in this case, any Java process could only use a maximum of 1024MB=1GB of memory. 2G means 2GB.

APP by default will start on a new installation with 2GB's of memory available. If this is not the case, then this environment variable is very likely to be set on your Operating System level.

If the variable is set, you will need to delete it (or alter it to influence the amount of memory that APP can use). Below are general instructions on how to find and delete the variable so APP can function properly :

Windows:

Right click on windows start:

System, system info, advanced system settings, Environment Variables

Here is an explanation as well:

https://www.computerhope.com/issues/ch000549.htm

MacOS & Linux:

This is probably a bit more complicated than on windows, because it can depend on which MacOS version you are or which shell you have on your Linux distribution, here is a general article that could help you in this regard:

https://support.foundry.com/hc/en-us/articles/209642805-Q100127-How-to-delete-unset-environment-variables

If you do a search on a searchengine, you are bound to found a way to solve this for your MacOS version or Linux distribution.

If you need help with deleting the envrionment variable on your computer, please let us know 😉

Kind regards,

Mabula

This topic was modified 2 years ago 5 times by Mabula-Admin

ReplyQuote
(@mikecmp)
White Dwarf Customer
Joined: 5 months ago
Posts: 19
June 22, 2020 15:50  

Actually, I think for the Mac version at least, this is a bug in the packaging of APP

Once installed, If I open contents of APP, and go into contents/java/AstropixelPriocessor.cfg There is a option under "JVMOptions" for -Xmx2g

The UI showed the correct value that I had set, but this file did not have the value updated. Once I changed this file and saved it, I saw APP use the correct amount of ram, or at least over 2gb 

I think that APP just needs to write the user specified value to this file as well and it would solve this problem on the Mac. 

 

Not a Java expert by any stretch! But this is how I solved the problem on my Mac

 

Mike


ReplyQuote
(@vincent-mod)
Universe Admin
Joined: 3 years ago
Posts: 2657
June 22, 2020 16:27  

Very interesting Mike, I'll forward this to Mabula.


ReplyQuote
(@mikecmp)
White Dwarf Customer
Joined: 5 months ago
Posts: 19
June 22, 2020 17:22  

Sure thing - I found it as the second answer here:

 

https://stackoverflow.com/questions/10887518/change-max-memory-heap-for-java-on-mac-os-x


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 4 years ago
Posts: 2476
June 24, 2020 15:10  
Posted by: @mikecmp

Actually, I think for the Mac version at least, this is a bug in the packaging of APP

Once installed, If I open contents of APP, and go into contents/java/AstropixelPriocessor.cfg There is a option under "JVMOptions" for -Xmx2g

The UI showed the correct value that I had set, but this file did not have the value updated. Once I changed this file and saved it, I saw APP use the correct amount of ram, or at least over 2gb 

I think that APP just needs to write the user specified value to this file as well and it would solve this problem on the Mac. 

 

Not a Java expert by any stretch! But this is how I solved the problem on my Mac

 

Mike

H Michael @mikecmp & @vincent-mod,

This is NOT AN ERROR of APP's packaging really. APP uses the java 8 packager.

This topic concern's operating system's where for some reason other software builders had a problem with packaging... 🙂

Setting Java options on the operating system level is not smart and older java software packages used to do this... so if the operating system has this value _JAVA_OPTIONS then you need to remove this and APP will work as expected and according to modern java packaging.

To be clear, a user should never have to alter : AstropixelPriocessor.cfg

You can simply click on the CFG button in APP to change memory of APP, it will be applied after a restart. And the CFG should NOT be adjusted, this is not how that works...

The UI showed the correct value that I had set, but this file did not have the value updated. Once I changed this file and saved it, I saw APP use the correct amount of ram, or at least over 2gb

I think that APP just needs to write the user specified value to this file as well and it would solve this problem on the Mac.

And this is controlled on the user level. The CFG file regarding JVMOptions" for -Xmx2g is for general first time installation. Once APP has been started, the actual configuration is saved on the user account on for instance MacOS and Windows. So, the cfg file should not be changed by the user !

On all MacOS versions from sierra to Catalina, app works properly with memory management using only the CFG button in APP. I have never instructed users to change the CFG file, and they shouldn't need to do so.

It will only NOT work if _JAVA_OPTIONS are set on the Operating System level, which you never want to do. Older MacOS installation with legacy software might have this issue and that issue is caused by legacy software NOT using proper packaging, really 😉

Mabula


ReplyQuote
(@mikecmp)
White Dwarf Customer
Joined: 5 months ago
Posts: 19
June 24, 2020 15:17  

Interesting - I will poke around more - for now modifying the config in the app works for me, I'll try to hunt down the root of the problem with the installed version of the software.

Its possible i set something up incorrectly - I used this machine for work for several clients, all of whom had different software versions , etc. So i probably have a config buried somewhere I did not uncover. 

 

Thanks for the response, appreciate it and love APP

 

Mike


ReplyQuote
Share: