gem install rails results in OutOfMemoryError

Can you try it again with RC3? If you get the OOM error, try passing -J-Xmx512M to JRuby when running gem, as in:

jruby -J-Xmx512M -S gem install ....

FYI, I have noticed tha AMD64 version of Java 6 always runs in server mode, which makes it slower to start up and makes it use more memory. I'm not sure if there are plans to release a non-server version or not.

Not sure if you fixed this issue intentionally, or as a by-product of addressing some other problem. In any case, using RC3 makes the OOM error go away. I did not have to use the -Xmx512m option, which is good. Thank you.

It's happening again with the JRuby 1.0 release. This time I'm running Fedora 6 and JDK 1.6.0 on an Ultra 20 (AMD Opteron) with 2GB of RAM. As before, I'm attempting to install the rails gems: gem install rails -y --no-rdoc

If I modify the jruby shell script, changing the JAVA_MEM environment variable to "-Xmx512m" then it works fine.

So, not a high priority, but I think this issue is worth tracking.

Downgrading this to major. I think this is one of those issues that is more sensitive than most to memory changes. While we do have improvements to make in that area, since we do have a workaround (-J-Xmx512m), this isn't as much of an issue.

It would be nice to know what gems were causing this. None I use ever cause OOM, but I often skip doc generation. If our default max heap isn't enough, we could probably bump it up without causing too many worries...but I'd like to know if there's a specific gem that's causing such headaches. Assigning to 1.1.

I'm getting this with xmpp4r, with trunk. All other gems I've tried seem to work fine. Seems odd, since xmpp4r is a small library.

Just noticed that this seems to occur on the "bulk updating..." phase, so perhaps it's got something to do with the number of gems installed ? I've got 20.

specifying the max memory fixes the install (as expected)

This was fixed on both trunk and 1_0 branch 'gem' scripts by specifying -J-Xmx384M in the shebang. We don't want to bump up the max heap for the normal jruby command right now, especially since you can just specify it yourself.

running "gem update" still throws the same exception on my system. running through jruby and specifying 512Mb max heap works. Maybe 384Mb is not enough ? I have 22 gems installed, including rails.

FYI, the fix that Charles made to the gem script shebang breaks on linux:

dylan@dylan:~/workspace/jruby_test$ $JRUBY_HOME/bin/gem list
/usr/bin/env: jruby -J-Xmx384M: No such file or directory

I believe this is due to linux's shebang handling:

http://en.wikipedia.org/wiki/Shebang_(Unix)#Portability

workaround is to call gem via:

jruby -S gem list

or

jruby -J-Xmx384M -S gem install rails -y --no-ri --no-rdoc

I'm running into this with 1.1.2 when trying to install rails. Apparently the default Xmx (500m?) is not enough, increasing it to 700m seems to help.

erno@satumaa:~$ java -version
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode)

erno@satumaa:~$ jruby -v
ruby 1.8.6 (2008-05-28 rev 6586) [amd64-jruby1.1.2]

erno@satumaa:~$ jruby -S gem install rails --no-ri --no-rdoc

=> results in
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at org.jruby.runtime.ThreadContext.popFrameReal(ThreadContext.java:354)
at org.jruby.runtime.ThreadContext.postYield(ThreadContext.java:889)
...