-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JRuby 9.0.1.0 takes > 500 MB of RAM to install bundler #3358
Comments
Hopefully useful info from another system where I can install bundler with a cap of 40MB:
@vassilevsky how many gems do you have installed before trying to install bundler? |
Bundler was the first gem I installed with
|
This is truly bizarre. A few things to do to get us more info:
|
The same on jruby 1.7.22 and the same machine as
Option
|
Does it work with explicit lower heap size? For example:
|
Sorry for the late reply. Had to use an older version of JRuby and encountered this issue again. Here are the details:
Full output: https://gist.github.com/vassilevsky/838666d4df0649e4ab27 Thank you 🙏 |
Anyone still able to reproduce this with JRuby 9.0.5.0? Another flag that could help us is the JVM flag @vassilevsky Your runhprof output was not as helpful as I'd hoped. :-( It doesn't show enough allocated objects to be a problem, so I'm starting to wonder if this is a native memory or resource leak of some kind. To anyone that can still reproduce it:
|
Yes, it is still there :( But I started suspecting the environment rather than JRuby itself. |
I was able to install bundler with -Xmx100M on Java 7 and 8, JRuby 9.0.5.0 and JRuby 9.1.0.0. This was on OS X We're going to need to get a heap dump from your JRuby instance when it's using all that memory, or I don't think we'll be able to investigate it. Do you have some JRUBY_OPTS in env we're not setting, or some libraries that are getting loaded by some other piece of code? |
@vassilevsky If you have a few minutes, you could stop into our IRC channel to work through this a bit. |
Seems environmental and no response from original reporter. Closing for now. |
Hello :)
I think JRuby is too memory-hungry.
Will happily provide any additional info you need.
The text was updated successfully, but these errors were encountered: