How to configure VM arguments to avoid "java.lang.OutOfMemoryError: Java heap space"

[MagIciaNGTAO]

Normally, we can use eclipse to do "run configuration" to configure VM arguments.

In "hellobioqa.launch" context, how should we configure the JVM parameter?

Tks!

team-16

[elmer-garduno]

Right click on the hellobioqa.launch > run configurations > (x)=arguments tab > VM Arguments >

There you can use the -Xmx512m or whatever amount you need.

[MagIciaNGTAO]

Thanks for your response!

But it seems not works in my context. This is the launch file.

"<"?xml version="1.0" encoding="UTF-8" standalone="no"?> "<"launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication"> "<"stringAttribute key="bad_container_name" value="/edu.cmu.lti.oaqa.openqa.HelloQA/launchers"/> "<"listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS"> "<"listEntry value="/hellobioqa"/> "<"/listAttribute> "<"listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES"> "<"listEntry value="4"/> "<"/listAttribute> "<"stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER" value="org.eclipse.m2e.launchconfig.classpathProvider"/> "<"stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="edu.cmu.lti.oaqa.ecd.driver.ECDDriver"/> "<"stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="hellobioqa.hellobioqa"/> "<"stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="hw2-team16"/> "<"stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER" value="org.eclipse.m2e.launchconfig.sourcepathProvider"/> "<"/launchConfiguration>

So nothing in the "run configuration" can fit for my launch purpose well ...

Is there any way to change inside the launch file?

BTW, I have put it into Stackoverflow, if there is any feedback, will let you know.

[MagIciaNGTAO]

Hi,

I have figured it out by creating a .launch file in another project by myself. The useful line is

"<"stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xmx2G"/>