While using gwtClassRun, users are likely to encounter problems while repeatedly refreshing the GWT browser. This is likely due to a memory leak in GWT. After several iteration of refresh, GWT’s browser complains of insufficient memory to run the application. Unfortunately this problem cannot be resolved completely rather it can only be alleviated. Either users have to enlarge the pool of memory available to GWT or rerun (Close and Rerun) the GWT browser.
At times, it will be more efficient to just assign it more memory so that browser can refresh properly rather than keep restarting the browser which incurs longer waiting time. To reduce the occurrence of insufficient memory due to memory leak, just increase the memory available to GWT. It will at least allows several more Refresh before user need to close the browser and rerun it.
Here’s how:
In a IDE’s configuration for running GWT application, add the VM parameter with
-Xmx128m
This means setting maximum heap memory available to a application to 128mb.
More info http://edocs.bea.com/wls/docs61/perform/JVMTuning.html
