I am developing a GWT application and am having problems with development mode testing in eclipse.
When I make changes to the client code, I refresh the browser page (F5) to reload the module. Every time I do this (the code has changed or not), the "Development" tab in eclipse shows a new marker point with "Loaded module xxxx". Also, according to the task manager, every time I do this, the javaw.exe host process increases by about 1 MB of memory. In the end (after 10-20 updates), the page does not load, and this error is displayed on the "Development Mode" tab:
Out of memory; to increase the amount of memory, use the -Xmx flag at startup (java -Xmx128M ...)
I can fix this by stopping and restarting the server (not the small update button on the Developer Mode tab, but the Red Stop button), but then the module needs to be reviewed, which takes some time. It seems that the eclipse does not understand that I ended up with the old module when I reboot the new one. I am observing the same behavior with a completely new GWT project, so I don't think this is my code. Does anyone know how to fix this?
EDIT : see both answers below for possible solutions.
source share