Re: [jruby-user] Re: Out of memory problem with JRuby-Complete

Christian MICHON <[email protected]>
Newsgroups gmane.comp.lang.jruby.user
Message-ID <CACx2yF8f5xS50pG2ZXy-JBP3t4=4Y0GPx4EuZBMBd9NXfKKXMw@mail.gmail.com>
Hi again,

so you're using a 32 bits version of the JVM. If you have the possibility
to use the 64 bits, please do so. Otherwise, you'll be actually limited to
~1.5Gb max.

I suggest -Xmx1400m or -Xmx1500m. You should use jvisualvm or jmc depending
on your JVM version, just to rule out java memory issues and maybe compare
possibly different behavior between jruby and jruby-complete...



On Tue, Aug 19, 2014 at 8:22 PM, Cees Zeelenberg <[email protected]>
wrote:

> Thomas E Enebo wrote in post #1155520:
> > E_OUTOFMEMORY looks more like a Windows error (via whatever is happening
> > in
> > win32ole) than a Java one but you may still want to use much more than
> > 500m
> > for max heap as a test.  I believe we actually specifiy more than that
> > from
> > jruby command-line.
> >
> > Also if you are on 32 bits you are limited to 3.2GB for a whole process
> > (I
> > think?).  If so then you might want to make sure something is not
> > leaking?
> >
> > -Tom
> >
> >
> >
> >
> > On Tue, Aug 19, 2014 at 6:12 AM, Cees Zeelenberg <[email protected]>
> I tried with much larger heapsize (up till getting at -Xmx2048m the
> errormessage "Could not reserve enough space for object heap") with no
> success. Somehow it seems to me that the amount of memory available for
> "native processes" within WIN32OLE does not depend on the heapsize. If
> it was caused by a major memory leak I would expect the same behavior
> under JRuby as when using JRuby-Complete
>
> =Cees
>
> --
> Posted via http://www.ruby-forum.com/.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>


-- 
Christian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.