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

I guess I am not surprised if you run out of memory the win32ole stuff is
not cleaning up the cocreated process.  The fact that this works with jruby
but fails with jruby-complete is the big clue.  For the life of me I don't
know what the difference could be however..

I don't have 32 bit windows nor MS Word so this is very diificult for me to
try stuff out...

-Tom



On Wed, Aug 20, 2014 at 3:12 AM, Cees Zeelenberg <[email protected]>
wrote:

> Thomas E Enebo wrote in post #1155533:
> > 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]>
> Hi Tom, thanks for spending your time on this.
> It fails the very first time (on WIN32OLE.new('Word.Application')) in
> org.racob.com.Dispatch.createInstanceNative
> it successfully executes a 'CoCreateInstance' and then fails  in
> 'QueryInterface' returning with hr=0x8007000e (E_OUTOFMEMORY)
> Interesting enough, when I look with the Windows Task Manager, each try
> creates an instance of WINWORD.EXE*32 which can only be removed by
> ending the process with the Window Manager.
>
> -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]