Eclipse Community Forums: Eclipse Platform » Heap memory problem [after changes based on documentation]

Home » Eclipse Projects » Eclipse Platform » Heap memory problem [after changes based on documentation]

Heap memory problem [after changes based on documentation] [message #335383]

Sun, 05 April 2009 17:32

Eclipse User

Hi

I am having a heap memory problem. I've read the appropriate documentation
(to list one:
http://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_ available_to_Eclipse%3F),
and I still am not able to fix my problem.

My eclipse.ini file currently looks like this:
///
-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101 .R34x_v20080731
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
128m
-vmargs
-Xms300m
-Xmx1024m
///

My stack trace is this:
+++
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.nio.CharBuffer.wrap(Unknown Source)
at sun.nio.cs.StreamEncoder.implWrite(Unknown Source)
at sun.nio.cs.StreamEncoder.write(Unknown Source)
at java.io.OutputStreamWriter.write(Unknown Source)
at java.io.BufferedWriter.flushBuffer(Unknown Source)
at java.io.PrintStream.write(Unknown Source)
at java.io.PrintStream.print(Unknown Source)
at java.io.PrintStream.println(Unknown Source)
at
edu.stanford.nlp.tagger.maxent.GlobalHolder.readModelAndInit (GlobalHolder.java:497)
at edu.stanford.nlp.tagger.maxent.MaxentTagger.init(MaxentTagge r.java:235)
at edu.stanford.nlp.tagger.maxent.MaxentTagger.init(MaxentTagge r.java:219)
at
edu.stanford.nlp.tagger.maxent.MaxentTagger.<init>(MaxentTagger.java:206)
at AutomaticGrader.main(AutomaticGrader.java:19)
+++

What I can infer is that the changes I did to the ini file have not
worked. No matter how many different sizes I try, I always get to the same
point in the program.

Other notes:
- I've gone to Help/About and clicked on "Configuration Details." My
config file settings seem to be correct there.
- I know for a fact, that 300Mb are enough to run my program... It isn't
actually mine and I can use it from the cmd line with max 300Mb.

Any thoughts?

~Kino

Re: Heap memory problem [after changes based on documentation] [message #335385 is a reply to message #335383]

Sun, 05 April 2009 23:15

Eclipse User

Kino Aguilar wrote:
> Hi
>
> I am having a heap memory problem. I've read the appropriate
> documentation (to list one:
> http://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_ available_to_Eclipse%3F),
> and I still am not able to fix my problem.
>
> My eclipse.ini file currently looks like this:
> ///
> -startup
> plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. jar
> --launcher.library
> plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101 .R34x_v20080731
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 128m
> -vmargs
> -Xms300m
> -Xmx1024m
> ///
>
> My stack trace is this:
> +++
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at java.nio.CharBuffer.wrap(Unknown Source)
> at sun.nio.cs.StreamEncoder.implWrite(Unknown Source)
> at sun.nio.cs.StreamEncoder.write(Unknown Source)
> at java.io.OutputStreamWriter.write(Unknown Source)
> at java.io.BufferedWriter.flushBuffer(Unknown Source)
> at java.io.PrintStream.write(Unknown Source)
> at java.io.PrintStream.print(Unknown Source)
> at java.io.PrintStream.println(Unknown Source)
> at
> edu.stanford.nlp.tagger.maxent.GlobalHolder.readModelAndInit (GlobalHolder.java:497)
>
> at
> edu.stanford.nlp.tagger.maxent.MaxentTagger.init(MaxentTagge r.java:235)
> at
> edu.stanford.nlp.tagger.maxent.MaxentTagger.init(MaxentTagge r.java:219)
> at
> edu.stanford.nlp.tagger.maxent.MaxentTagger.<init>(MaxentTagger.java:206)
> at AutomaticGrader.main(AutomaticGrader.java:19)
> +++
>
> What I can infer is that the changes I did to the ini file have not
> worked. No matter how many different sizes I try, I always get to the
> same point in the program.
> Other notes:
> - I've gone to Help/About and clicked on "Configuration Details." My
> config file settings seem to be correct there.
> - I know for a fact, that 300Mb are enough to run my program... It isn't
> actually mine and I can use it from the cmd line with max 300Mb.
>
> Any thoughts?
>
> ~Kino
>
>
From the stack trace that you provided, it looks like you are running a
Java application. Changing the eclipse.ini file doesn't have any effect
on applications run from within Eclipse. The eclipse.ini file changes
would be appropriate if Eclipse were running out of memory. I'm
guessing that your application is running out of memory when you are
launching it from within Eclipse.

You will need to set the vm arguments in the launch configuration of
your application. Use the Run->Run Configuration... menu to open up the
launch configurations defined in your workspace. Select the launch
config for your application and enter the appropriate vm arguments on
the Arguments tab.

Previous Topic:	Common Navigator and Tabbed Properties View
Next Topic:	Notification on Editor close

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Oct 26 09:45:30 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter