Description of problem: When starting SBT, Java reports cannot start VM because it cannot reserve enough heap. Version-Release number of selected component (if applicable): 0.13.1 How reproducible: Every time on my machine. Steps to Reproduce: Run command sbt in console and see the console output. Actual results: ''' $ sbt Error occurred during initialization of VM Could not reserve enough space for object heap Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. ''' Expected results: SBT works fine. Additional info: My machine is 32-bit. When I start SBT, my memory usage is 0.8 GiB / 2.5 GiB, swap usage 0 GiB / 3.8GiB. But after I modified the memory settings of Java in my SBT script (/usr/bin/sbt), I can run it. These are the last few lines of my modified: ''' export BASE_CLASSPATH=$(build-classpath scala ivy sbt ${JLINE} jansi test-interface sbinary) export JAVA_OPTS="-Xms256m -Xmx1024m -Xss1M -XX:+CMSClassUnloadingEnabled -XX:MaxHeapSize=1000m -XX:MaxPermSize=256m" java ${JAVA_OPTS} -Dfedora.sbt.boot.dir=${SBT_BOOT_DIR} -Dfedora.sbt.ivy.dir=${SBT_IVY_DIR} -Dsbt.boot.properties=${SBT_BOOT_PROPERTIES} -cp ${BASE_CLASSPATH} xsbt.boot.Boot "$@" ''' This is the StackOverflow question where I found my way: https://stackoverflow.com/questions/4401396/could-not-reserve-enough-space-for-object-heap
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.