Ok. I'll do that.
Is there any workaround, in the meantime?
Charles Oliver Nutter wrote:
Eric Armstrong wrote:
Eric Armstrong wrote:
Aha. I see that change has to be made to the
first line of the gem script in <jruby_install>/bin
#!/usr/bin/env jruby -J-Xmx784M
Yow. But even that change was insufficient. So I tried
the same settings we use for monster javadoc builds:
#!/usr/bin/env jruby -J-Xms128M -J-Xmx1024M
But that still didn't work. Is a sub-process being fired
off that isn't using those settings?
This looks more like a bug, something running away in jvyamlb. Can you
report this in JIRA?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Eric Armstrong, Document Systems Architect, Sun Microsystems
http://blogs.sun.com/coolstuff
http://www.artima.com/weblogs/index.jsp?blogger=cooltools
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
