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

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]>
wrote:

> Hi,
> I am working on a windows desktop application where I use JRuby for
> developing the application and JRuby-Complete to package the application
> in a jar. The application uses a fair number of external libraries -
> including Qt for the user interface - but so far I have had no trouble
> in running the packaged version once the JRuby version worked.
> Recently I added functionality to the application to interoperate with
> Microsoft Word using WIN32OLE. This works very nicely under JRuby using
> the jruby-win32ole-0.8.5 gem, but when I run the same program using
> JRuby-Complete, I consistently get the errormessage :
>
>    "Can't QI object for IDispatch"
>
>  Inspecting the error condition that leads to this message, it appears
> that the interfacing software in the gem runs out of memory ( Windows
> error: 0x8007000E ; E_OUTOFMEMORY).
> I don't know if there is a difference in memory allocation policy
> between the two JRuby implementations. I have experimented with
> explicitly setting heap and stacksizes for JRuby-Complete e.g.
>
> java -Xms256m -Xmx500m -Xss1024k -cp
> lib\java\jruby-complete-1.7.13.jar;(other jars) org.jruby.Main
> src\jruby_bootstrap.rb
>
> But that made no difference to the error.
>
> Any suggestions how I may solve this problem are very welcome
>
> Cees Zeelenberg
>
> --
> 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]