by Jon (Updated on 2015-10-13)
The Java runtime reserves a chunk of memory for Stencyl to use before launching -- it can't be raised after the fact. If you exceed this limit, Stencyl locks up.
So why not just set the limit very high? It causes machines with less memory to fail to launch Stencyl at all.
Although we are working to reduce memory usage and plug leaks, there are large games for which having the higher memory usage is useful. This guide explains how you can raise the limit.
Common Misconception: The 90% memory warning has nothing to do with how much RAM your computer has. You could have 128 GB of RAM and still hit this since Java's upper cap sits around 4 GB and on some systems, may be as low as 2 GB.
Install the 64-bit version (x64) of Java 8 to your computer.
Download one of the following scripts and place it into your Stencyl installation directory. (For best results, go lower than what you have -- e.g. If you have 4 GB, choose the 2 or 3 GB option.)
Note 1: If Stencyl fails to launch, choose a script with a lower amount of memory.
Note 2:Note: The -Xmx setting in the script may be overridden by the _JAVA_OPTIONS environment variable. See this tutorial for how to delete the variable.
Right-click the Stencyl.app bundle and pick Show Package Contents.
Using a text editor, open up Contents/MacOS/Stencyl.
Search for -Xmx1536m and change the number to something higher such as 3072 (which would be 3 GB).
Note: If Stencyl fails to launch after you make an edit, your number is too high. Try something smaller such as 2048.
Edit the Stencyl shell script.
Note: If Stencyl fails to launch after you make an edit, your number is too high. Try something smaller such as 2048 or 3072.