Languages that provide no compilation or simple compilation don’t require the changes to the eclipse.ini for a bigger stack size and more memory.
It would be nice to have a flag in ESV to turn off the Spoofax Configuration Warning for such languages.

On startup of Eclipse, we could check the flag for all registered languages and decide whether to show the warning or not.

It may be necessary to fix https://yellowgrass.org/issue/Spoofax/845 first. The problem now is that all metalanguages get deployed whenever you deploy some language, so the warning would still show up if it’s enabled by one of the meta languages.

Submitted by Oskar van Rest on 4 November 2014 at 21:49

Fixed with https://github.com/metaborg/spoofax/pull/10

Add jvm opts: -Xmx512m to your editor/yourlang.main.esv.

This sets the maximum heap size required for your language to 512m. If there are no other languages loaded that require a higher maximum heap size, the configuration warning won’t appear since Eclipse by default starts up with -Xmx512m or -Xmx1024m (>= -Xmx512m).

Also, there is the -Xss option to set the stack size. By default, eclipse.ini does not specify a stack size. A default stack size is chosen, which is platform specific: https://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionX.html#wp1024112
Leaving away the -Xss option in editor/yourlang.main.esv means that your language does not require more than the default stack size. The configuration warning will therefore only appear if at least one of the loaded languages has the -Xss option enabled, in which case eclipse.ini should be configured with the highest required stack size among the languages. The configuration warning will tell what the highest value is.