-
Bug
-
Resolution: Invalid
-
None
-
1.2.1
-
None
-
None
-
System.getProperty('os.name') == 'Windows 7'
System.getProperty('os.version') == '6.1'
System.getProperty('os.arch') == 'amd64'
System.getProperty('java.version') == '1.7.0_25'
System.getProperty('java.vendor') == 'Oracle Corporation'
System.getProperty('sun.arch.data.model') == '64'
JVM Args: -Xmx1024M -Xms1024MSystem.getProperty('os.name') == 'Windows 7' System.getProperty('os.version') == '6.1' System.getProperty('os.arch') == 'amd64' System.getProperty('java.version') == '1.7.0_25' System.getProperty('java.vendor') == 'Oracle Corporation' System.getProperty('sun.arch.data.model') == '64' JVM Args: -Xmx1024M -Xms1024M
-
Unconfirmed
Crashes with :
Client> Error occurred during initialization of VM Client> Incompatible minimum and maximum heap sizes specified Client> Picked up _JAVA_OPTIONS: -Xmx512M Game ended with bad state (exit code 1) Ignoring visibility rule and showing launcher due to a game crash
Seems to appear that the Xms tag is read but the Xmx tag is ignored, meaning that Xms > Xmx, which results in the crash.
Reasons to believe this:
"Client> Picked up _JAVA_OPTIONS: -Xmx512M" in log suggests that it is forced to run with 512 MB of RAM. Running with JVM args "-Xmx2048M -Xms512M" works fine but with "-Xmx2048M -Xms513M" still crashes.
- is duplicated by
-
- Resolved
-
- Resolved
-
- Resolved
-
- Resolved
-
- Resolved