Heap problems in Eclipse?

[davetheant]

Hello everyone. I am getting OOME's in Eclipse when trying to run my code. I added -Xms and -Xmx arguments to my eclipse.ini file (under the vmargs section), and gave them a generous 800mb. When I open Eclipse, I see that the bar showing my heap has a new max of 800mb. When I run my code, however, the 'used' bar never goes past 40mb, but I get the error. I even changed my run settings and put in -Xms and -Xmx args there as well.

[masijade]

Go to the run configuration and and add those options to the VM arguments text area on the arguments tab.

[davetheant]

I did that as well to no avail.

[Norm]

What is your code doing that makes it run out of memory? Do you have a recursive loop?

Try catching the exception and printing the stack.

[Fubarable]

what exactly is your error message? Are you running out of stack memory? Do you have uncontrolled recursion going on?

[JosAH]

what exactly is your error message? Are you running out of stack memory? Do you have uncontrolled recursion going on?

Nope, the OP ran out of heap memory, hence the OOME, otherwise a StackOverflowError would've been thrown; it's some sticky memory that can't be released because the OP's classes still have a reference to the objects.

kind regards,

Jos

[masijade]

You also get OOME's for to many handles and/or too many threads, etc. You do know that, right?
That was meant for the OP, BTW.

[davetheant]

I think the problem was trying to create an array with too many elements, but I really didn't think two arrays of longs with 10,000 elements each should really make a problem. I found another way to solve the assignment, but I still would like to solve the heap problem. The error was just the regular out of memory: heap

[masijade]

That is only 160k. Now a two-dimensional array of 10,000 elements in each "level" is another story.

That is, of course, 800 Mb, then.