Startup Issue with Application Deployment - Java repeatedly killed - memory allocation

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Callisto’ v2.5.0.4 (Mainline)
Virtualization QEMU_KVM
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

Java is repeatedly being killed with exit status 137, indicating it’s being killed by the OS to free up memory. I have Java set to use 7gb out of the 8gb for the server. I figured this would provide enough of a buffer, but maybe not. What are the memory guidelines for these instances?

Reproduction Steps

  • go to instances in the game panel, open the minecraft instance
  • Go to Java settings in the game panel and set memory allocation to 7gb
  • Start the minecraft instance and wait. Eventually the instance is killed (sometimes several times a day)
2

The operating system itself uses some ram, and some modpacks tend leak and cause for Java to “outgrow” the amount of ram you have dedicated, so you may need to lower it to something like 6GB, or restart the server more frequently using the scheduler to clear up the memory leaks.
If you continue to have issues you might need to get more ram for whatever PC or VPS you’re using to host AMP. (if it’s the latter, that would be something you’d need to talk to your hosting provider about)

1 Like