Saturday, December 23, 2017

SuperDevMode OutOfMemoryError


We have a large project with about 250 KLoC client-side code (without comment and blank lines). This project compiles in DevMode with Xmx2500m in 3mins. But in SuperDevMode it throws OutOfMemoryError.

GWT Libraries: GWT 2.8.2, gwittir, gwtchosen, gwtquery

Compiler Arguments: org.example.base.Base -startupUrl base -war /usr/jboss/standalone/deployments/base.war -noserver -logLevel ERROR -port 80 -nosuperDevMode -XmethodNameDisplayMode FULL -strict

VM Arguments: -Xms2000m -Xmx2500m -XX:+UseCompressedOops${TMP}/base -Dgwt.persistentunitcachedir=${TMP}/base -Dgwt.usearchives=true -Dgwt.disableGeneratorResultCaching

Just change -nosuperDevMode to -superDevMode in compiler arguments.

In DevMode with Xmx2500m, first compile takes about 3min, but in SuperDevMode with even Xmx4000m it throws OutOfMemoryError. By increasing Xmx to 20GB, it starts compile but never stops (it seems it needs more memory). So we can not use SuperDevMode in large projects. (Removing gwt.usearchives or gwt.disableGeneratorResultCaching has no effect.)

My questions:

1. Why SuperDevMode should takes more memory than DevMode?

2. In small projects, SuperDevMode compile time is equal or greater than DevMode compile time. Is it normal?

3. How can I reduce SuperDevMode compile time?


You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment