David Newton wrote:I just change the -vmargs options in eclipse.ini; works for me. IIRC there are requirements for the -Xmx argument, like a multiple of 1024 or something, but I don't have an installation in front of me to check.
David Newton wrote:If I Remember Correctly--sorry!
What about MaxPermSize?
Peter Johnson wrote:Let me see if I understand this correctly. If you run your application standalone, then setting -Xmx1024m works and the app runs fine. Is that correct? If so, setting the max heap to 1024m in Eclipse will not work because Eclipse itself takes up a large amount of heap. I would try setting it to -Xmx1536m, or whatever the largest heap you can manage on your machine. That should give enough room for Eclipse and your app. Of course, if you plan to debug you might need more room...
The above assume that you are running your app in the same JVM as Ecipse, and not forking your app off into a separate JVM.
Also, you might want to set -XX:+HeapDumpOnOutOfMemoryError. Then when you get a OOME you will also get a heap dump file which you can load into VisualVM, Eclipse MAT, or some other tool and examine what is using up all the heap memory.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton