[
https://issues.apache.org/jira/browse/GROOVY-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672184#comment-16672184
]
Paul King commented on GROOVY-8865:
-----------------------------------
Okay, understood. Looks like we hard code a value for -Xmx:
https://github.com/apache/groovy/blob/master/src/bin/startGroovy.bat#L262
Obviously we should not do that if a user supplies their own -Xmx and/or the
value should be at least as big as any -Xms setting.
> 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
> Priority: Major
>
> 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)
