[Bug 1144270] New: SBT doesn't start correctly in some 32-bit machines due to low memory
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1144270
Bug ID: 1144270
Summary: SBT doesn't start correctly in some 32-bit machines
due to low memory
Product: Fedora
Version: 20
Component: sbt
Assignee: willb(a)redhat.com
Reporter: dugucloud(a)qq.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io,
willb(a)redhat.com
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-spac...
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sZuZ0ALIyT&a=cc_unsubscribe
8 years, 9 months
[Bug 1090765] New: Scala projects containing the sbteclipse plugin fail to build
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1090765
Bug ID: 1090765
Summary: Scala projects containing the sbteclipse plugin fail
to build
Product: Fedora
Version: 20
Component: sbt
Severity: high
Assignee: willb(a)redhat.com
Reporter: gvdmer(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io,
willb(a)redhat.com
Description of problem:
Scala project will not build in sbt 0.13.1 and Scala 2.10.3 unless I DO NOT try
to add the sbteclipse plugin (2.4.0)
Version-Release number of selected component (if applicable):
sbt 0.13.1
How reproducible:
Every time.
Steps to Reproduce:
1. "yum install -y java", "yum install -y scala", and "yum install -y sbt."
This installed OpenJDK 1.7.0_51, Scala 2.10.3, and sbt 0.13.1.
2. plugins.sbt contains the line "addSbtPlugin("com.typesafe.sbteclipse" %
"sbteclipse-plugin" % "2.4.0")"
Actual results:
Building the project generates the following error:
"sbt.ResolveException: unresolved dependency:
org.scala-lang#scala-library;2.10.3: configuration not found in
org.scala-lang#scala-library;2.10.3: 'compile'."
Expected results:
Project builds.
Additional info:
This is a problem whether the plugins.sbt is located in /project, or in
~/.sbt/0.13/plugins.
I encountered this problem attempting to build
https://github.com/liftmodules/widgets
When I comment-out the "addSbtPlugin.... sbteclipse-plugin" line from the
plugins.sbt, the build functions normally.
I recreated the problem using a simple test project that just creates a single
Scala class with a one-line print statement. The problem continues to occur
independently of whatever other plugins, repositories, or library dependencies
I define in the plugins.sbt and build.sbt files.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=1ghlw6cYfy&a=cc_unsubscribe
8 years, 9 months
[Bug 1083130] New: Memory options should not be set in /usr/bin/sbt
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1083130
Bug ID: 1083130
Summary: Memory options should not be set in /usr/bin/sbt
Product: Fedora
Version: 20
Component: sbt
Assignee: willb(a)redhat.com
Reporter: rocketraman(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
skottler(a)redhat.com, willb(a)redhat.com
Description of problem:
/usr/bin/sbt sets the JVM memory options for sbt. Also, the values are not sane
-- the max perm gen size is left at the default of 64 MB which is too small.
When running the upstream version of sbt, the memory and GC options by default
are:
-Xms1024m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=128m
When running the Fedora version of sbt, the options are:
-Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled
This is surprising behavior to say the least. In addition, the Fedora options
cannot be overwridden because /usr/bin/sbt does not check if JAVA_OPTS is
already defined before clobbering it.
Version-Release number of selected component (if applicable):
sbt-0.13.1-5.fc20.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=lrpKiQOfRe&a=cc_unsubscribe
8 years, 9 months
[Bug 1021292] New: Transaction check error when upgrading jogl2
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1021292
Bug ID: 1021292
Summary: Transaction check error when upgrading jogl2
Product: Fedora
Version: 20
Component: jogl2
Assignee: c.david86(a)gmail.com
Reporter: asaha(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: c.david86(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org
Description of problem:
# rpm -q jogl2
jogl2-2.0-0.11.rc12.fc20.x86_64
# yum -y update jogl2
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package jogl2.x86_64 0:2.0-0.11.rc12.fc20 will be updated
---> Package jogl2.x86_64 0:2.0.2-1.fc20 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
==============================================================================================================================================================================================
Package Arch
Version Repository
Size
==============================================================================================================================================================================================
Updating:
jogl2 x86_64
2.0.2-1.fc20 updates-testing
4.0 M
Transaction Summary
==============================================================================================================================================================================================
Upgrade 1 Package
Total size: 4.0 M
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/share/doc/jogl2/bouml from install of jogl2-2.0.2-1.fc20.x86_64
conflicts with file from package jogl2-2.0-0.11.rc12.fc20.x86_64
Error Summary
-------------
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. See above
2.
3.
Actual results:
Expected results:
Clean ugpgrade
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YU8riko2Sl&a=cc_unsubscribe
8 years, 9 months