Memory errors

[loachman]

I have all of the sudden out of the blue started getting memory errors on every project old and new.

[ERROR] Out of memory; to increase the amount of memory, use the -Xmx flag at startup (java -Xmx128M ...)

Anyway I can fix this in the GWT Designer? And what would all the sudden start causing errors like that I wonder?

Thanks
Loachman-

[Eric Clayberg]

I have all of the sudden out of the blue started getting memory errors on every project old and new.
[ERROR] Out of memory; to increase the amount of memory, use the -Xmx flag at startup (java -Xmx128M ...)
Anyway I can fix this in the GWT Designer? And what would all the sudden start causing errors like that I wonder?

Why are you assuming it is a GWT Designer issue?

What are you doing when you see these errors?

What exact version/build of Eclipse are you using?

How much memory do you have assigned to run Eclipse?

If you turn on the Heap Status indicator in Eclipse, what does it show?

[loachman]

Hi,

I have gotten this resolved on an "older box" of mine, strange as it may be. This box has less ram the CPU is older, etc..
But it is working for now so I am happy until I can pinpoint the problem.

[Eric Clayberg]

The amount of ram on the box rarely is an issue.

The amount of memory assigned to Eclipse is the issue.

[loachman]

Maybe I spoke too soon.
I am using the beta release.

I have a project I created via the command line. It works in eclipse just fine until I install GWT Designer then upon trying to run it I get the following errors.

[ERROR] Failure to load module 'com.sinewavemultimedia.metronome.SliderApp'
java.lang.OutOfMemoryError: Java heap space
at com.google.gwt.dev.javac.TypeOracleMediator.parseMetaDataTags(TypeOracleMediator.java:151)
at com.google.gwt.dev.javac.TypeOracleMediator.resolveMethod(TypeOracleMediator.java:1031)
at com.google.gwt.dev.javac.TypeOracleMediator.resolveMethods(TypeOracleMediator.java:1044)
at com.google.gwt.dev.javac.TypeOracleMediator.resolveTypeDeclaration(TypeOracleMediator.java:1434)
at com.google.gwt.dev.javac.TypeOracleMediator.refresh(TypeOracleMediator.java:382)
at com.google.gwt.dev.javac.CompilationState.compile(CompilationState.java:102)
at com.google.gwt.dev.cfg.ModuleDef.updateTypeOracle(ModuleDef.java:477)
at com.google.gwt.dev.cfg.ModuleDef.getTypeOracle(ModuleDef.java:324)
at com.google.gwt.dev.GWTShell$BrowserWidgetHostImpl.createModuleSpaceHost(GWTShell.java:253)
at com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.gwtOnLoad(BrowserWidgetIE6.java:67)

Also trying to run the new GWT_EXT for the 5.0.1 beta Release gives similiar errors.

I put the following into the eclipse.ini my computer has 512MB of ram (well this particular box anyways)
--launcher.XXMaxPermSize
512m
-vmargs
-Xms40m
-Xmx512m

[Eric Clayberg]

What exact version of Eclipse?

[loachman]

Using gandymede

Version: 3.4.0
Build id: I20080617-2000


Thanks

[Konstantin.Scheglov]

Maybe I spoke too soon.
I am using the beta release.

[cut]

I put the following into the eclipse.ini my computer has 512MB of ram (well this particular box anyways)
--launcher.XXMaxPermSize
512m
-vmargs
-Xms40m
-Xmx512m

Can you check that your Eclipse/JVM is really configured for enough memory?
Turn ON "Show heap status" in Window | Preferences | General and check max memory limit, also look how it is changed during parsing.

I use following JVM args "-XX:MaxPermSize=128m -Xms256m -Xmx256m" and this is more than enough to open simple GWT module (but with EXT GWT library attached, so it is also compiled).

[loachman]

Hi,

Using the settings you suggested. The heap status showed 40 of 256 when trying to parse and run the application.

I am using java 1.5.0_16 as my jdk, wonder if I should try a different one, or try eclipse 3.3.x again maybe.

Thanks

[Konstantin.Scheglov]

Hi,

Using the settings you suggested. The heap status showed 40 of 256 when trying to parse and run the application.

Run?
Do you open some of your form in GWT Designer visual editor?
Or you really run your GWT application?

For run you should set memory for your launch configuration, see attached.
For GWT 1.5 default 64m heap is not enough, I set at least 128m.

I am using java 1.5.0_16 as my jdk, wonder if I should try a different one, or try eclipse 3.3.x again maybe.

I use Java6 and Eclipse 3.4 release.

[loachman]

That worked the magic.

Thanks

[Eric Clayberg]

I'm glad that worked for you.

[eduxativa]

Maybe I spoke too soon.
I am using the beta release.

[cut]

I put the following into the eclipse.ini my computer has 512MB of ram (well this particular box anyways)
--launcher.XXMaxPermSize
512m
-vmargs
-Xms40m
-Xmx512m

Can you check that your Eclipse/JVM is really configured for enough memory?
Turn ON "Show heap status" in Window | Preferences | General and check max memory limit, also look how it is changed during parsing.

I use following JVM args "-XX:MaxPermSize=128m -Xms256m -Xmx256m" and this is more than enough to open simple GWT module (but with EXT GWT library attached, so it is also compiled).

Hi, i have the same problem, i turn on show heap status, but i don't know to check max memory limit, how i can do it please?
i,m using designer 5.1 beta and eclipse 3.4 with 3.3 had the same problem.
sorry for my english...
thanks

[Eric Clayberg]

i don't know to check max memory limit, how i can do it please?

The max memory limit used by Eclipse is whatever you set it to in the Eclipse startup parameters (typically set in the eclipse.ini file).

[eduxativa]

i don't know to check max memory limit, how i can do it please?

The max memory limit used by Eclipse is whatever you set it to in the Eclipse startup parameters (typically set in the eclipse.ini file).

-startup
plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Xms256m
-Xmx256m

this is my .ini file

But i have the same problem

[ERROR] Failure to load module 'com.mycompany.project.ImageViewer'
java.lang.OutOfMemoryError: Java heap space
at org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:459)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:411)
at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:275)
at com.google.gwt.dev.javac.JdtCompiler.compile(JdtCompiler.java:194)
at com.google.gwt.dev.javac.CompilationState.compile(CompilationState.java:72)
at com.google.gwt.dev.cfg.ModuleDef.updateTypeOracle(ModuleDef.java:477)
at com.google.gwt.dev.cfg.ModuleDef.getTypeOracle(ModuleDef.java:324)
at com.google.gwt.dev.GWTShell$BrowserWidgetHostImpl.createModuleSpaceHost(GWTShell.java:253)
at com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.gwtOnLoad(BrowserWidgetIE6.java:67)
at com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.invoke(BrowserWidgetIE6.java:128)
at com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java:294)

[ERROR] Out of memory; to increase the amount of memory, use the -Xmx flag at startup (java -Xmx128M ...)