Eclipse Space Capture (memory error)

Question

I am facing a memory issue in eclipse. I initially got this error: "Unhandled java java loop event empty space of the loop, and also sometimes" Error out of memory ".

I somehow managed to increase the heap size to -Xmx990m. But still it doesn’t work. When I try to increase the heap size beyond this, I get the error "Unable to create virtual machine when starting eclipse.

I tried to make other changes to the eclipse.ini file. When I change XXMaxPermSize, it gives me permGen memory error. Over the course of several times, I received various other errors, such as “Fixed limit for unprocessed event processing cycles”, as well as more than 2-3 different types. Please help me what can be done that would be great!

Answer 1

Jeshurun's somewhat frivolous comment about buying more RAM is actually pretty accurate. Eclipse is the memory of HOG! On my machine, right now, Eclipse is using 2.1 GB; no kidding. If you want to use Eclipse effectively, with all the great features, you really need a lot of memory.

As the saying goes, there are ways to use Eclipse with less memory. The biggest helper I found disables ALL validators (check "Suspend all validators" in the "Window"> "Settings"> "Check" section, just disconnecting individual ones will not help). Another common source of memory-suckage are plugins. If you stay in your current memory limit, I highly recommend you:

• Delete current Eclipse
• Download the main / stand-alone / just version of Java Eclipse (the one with the minimum file size / without plug-ins)
• Try using this for a little while longer and see how performance works. If everything is all right, try installing the plugins you like one at a time. Never install multiple and give each week or two trial versions.
• You will probably find that some plugins significantly increase memory usage; do not use them (or, if you want, get more RAM).

Hope this helps.

Answer 2

I also ran into the same problem. I decided to complete the build by following these steps:

-> Right click on the project, select RunAs → Run configurations

Select the project as BaseDirectory. Instead of goals, give eclipse: eclipse install

-> In the second tab, specify -Xmx1024m as the arguments to VM.

Answer 3

I faced a similar situation. My program was supposed to run a simulation for 10,000 samples. I tried -Xmx1024m: it crashed anyway.

Then I realized, given that my program is too much to put up with the console; my console memory can go OOB.

Easy solution => right-click console> settings> output of the final console Limit Check> Enter the buffer size (characters) [default: 80000].

I did not test it for a single run analysis, but when there were 10,000 samples in the final run, it started to fail, passing 500 tests.

Today was a day: I thought three times that how Java programming helps me skip all the freed memory and curse C for the same thing. And so, I spent the last 2 1/2 hours to find out how to get GC, how to remove the variable (by the way, not one was needed).

Have a nice day!