[ https://issues.apache.org/jira/browse/GROOVY-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King resolved GROOVY-8865. ------------------------------- Resolution: Fixed Assignee: Paul King Fix Version/s: 2.5.4 3.0.0-alpha-4 I have removed our explicit setting. Reading up on the default value for that setting on current JVMs, I suspect it will be set to a higher value on most folks systems. > Specifying initial heap size results in an error > ------------------------------------------------ > > Key: GROOVY-8865 > URL: https://issues.apache.org/jira/browse/GROOVY-8865 > Project: Groovy > Issue Type: Bug > Components: groovy-runtime > Affects Versions: 2.5.3 > Environment: Windows 10, OpenJDK 11.0.1 > Reporter: Rostyslav Smirnov > Assignee: Paul King > Priority: Major > Labels: contrib > Fix For: 3.0.0-alpha-4, 2.5.4 > > > On Windows, setting initial heap size greater than 128MB without setting > maximum heap size, e.g. JAVA_OPTS=-Xms1G, results in the following error: > {quote}Error occurred during initialization of VM > Initial heap size set to a larger value than the maximum heap size > {quote} > This works fine on Linux. And it is a valid JVM parameter, since JVM will set > its maximum heap to be the greater of its default value and initial heap size. -- This message was sent by Atlassian JIRA (v7.6.3#76005)