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

Thomas E Enebo <[email protected]>
Newsgroups gmane.comp.lang.jruby.user
Message-ID <CAL5zZVkFHCxXkVvqvp58brvq7-o5reW2WypHJXZk0BagbAnKbg@mail.gmail.com>
Yeah sorry I missed the part where you say this works with a regular
install of JRuby but not with jruby-complete.  I agree native memory will
be competing with the heap for overall process space.  I was just unclear
whether this was really a native memory error or not (although it looked
like it).

Does it work for a while and then give you this error or is it right away?

-Tom



On Tue, Aug 19, 2014 at 1: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
>
>
>


-- 
blog: http://blog.enebo.com       twitter: tom_enebo
mail: [email protected]
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.