Re: GWT Compiler

4 views
Skip to first unread message
Message has been deleted

Jason Essington

unread,
Mar 5, 2007, 10:11:12 AM3/5/07
to Google-We...@googlegroups.com
Nope, that is the solution, you need to bump the heap space via -Xms
and -Xmx

If you are compiling via the shell scripts, you can simply add those
switches to the script, something like:

java -XstartOnFirstThread -Xms128m -Xmx256 -cp ...
com.google.gwt.dev.GWTCompiler ...

in ant you just add them as jvmargs to the GWTCompiler invocation:
<java classname="com.google.gwt.dev.GWTCompiler"
fork="true"
failonerror="true"
dir="."
>
<jvmarg value="-XstartOnFirstThread" />
<jvmarg value="-Xms256m" />
<jvmarg value="-Xmx512m" />
<jvmarg value="-server" />
...

Or in eclipse, add them as "VM arguments" in the launch configuration
select "Run ..." or "Debug ..." then select your module
configuration, and look at the Arguments tab.

-jason

On Mar 3, 2007, at 8:00 AM, core wrote:

>
> Due compiling my gwt module i catch this error:
> Analyzing permutation #1
> [ERROR] Unexpected internal compiler error
> java.lang.OutOfMemoryError: Java heap space
>
> How can i push -xms or (and) -xmx parameters to gwt compiler?
> Or may be this problem has another solution?
>
>
> >

Reply all
Reply to author
Forward
0 new messages