Solutions for GC overhead limit exceeded appear

"An internal error occurred during:" Build project "occurs when I create a MAVEN project using the Myeclispe IDE. GC overhead limit Exceeded ", just beginning to think I clean a bit, and then restart MyEclipse on it, and later found not so. Since the error is going to find the root of the problem, then where is the problem?

In solving this problem, I looked for some information and found that the GC overhead LIMT exceed check is a strategy defined by hotspot VM 1.6 to predict whether or not to oom by counting GC time, and to throw an exception early to prevent Oom from happening. Sun officially defines this as: "The parallel/concurrent collector throws Outofmemroyerror when the GC is recycled too long." The long definition is that more than 98% of the time is spent doing GC and recovering less than 2% of heap memory. Used to avoid too little memory to cause the app to not work properly

This time need to seriously consider, since it is the configuration of memory out of the problem, then should go to the corresponding configuration file to find, MYECLISPE IDE related memory configuration file in Myeclispe.ini, of course, when we open it will be clear to see the following section of the code:

<span style= "Background-color:rgb (51, 255, 51); > #utf8 (Do not remove)
-startup
Plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-- Launcher.library
plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700
-VM
binary/com.sun.java.jdk7.win32.x86_64_1.7.0.u45/bin/javaw.exe
-install
D:\mytools\MyEclipse
- Vmargs
-xmx768m
-xx:maxpermsize=320m
-xx:reservedcodecachesize=64m
-dosgi.nls.warnings= Ignore</span>

It is clear that there is a section of-xmx768m configuration, it is as the largest memory, when the error occurred at the time of the present has exceeded this setting value, so we can make this maximum occupied memory to modify, adjusted to 1024m, the current setting is enough to use the value, Of course, some people will say "-xx:maxpermsize", also set to 1024m or larger, but I do not feel necessary, when we compile the file to let it always in the largest memory, often will appear the program stuck phenomenon. So everything is to be based on specific circumstances to do specific analysis and solve, to achieve the best results.