Eclipse: An internal error occurred during: & quot; Build Project & quot;. GC overhead limit exceeded, overheadexceeded

Eclipse: An internal error occurred during: "Build Project". GC overhead limit exceeded, overheadexceeded

When using the Eclipse Build Project function, the following error is prompted:
An internal error occurred during: "Build Project". GC overhead limit exceeded


The search result belongs to java. lang. OutOfMemoryError.
As we all know, the JVM memory overflows. What about GC overhead limit exceed?

GC overhead limt exceed check is a policy defined by Hotspot VM 1.6. It uses GC time statistics to determine if OOM is required. An exception is thrown in advance to prevent OOM. Sun officially defines this as: "the parallel/concurrent recycler will throw an OutOfMemroyError when the GC collection time is too long. The definition is that more than 98% of the time is used for GC and less than 2% of heap memory is recycled. It is used to prevent applications from running properly due to too small memory. "

It Sounds useless... How to predict OOM? At first, this tool can only be used to Catch and release memory resources to avoid application failures. Later, it was found that this policy cannot save your application, but you can make the final struggle before the application fails, such as data storage or on-site storage (Heap Dump ).

In addition, this policy may also cause problems, such as frequent OOM when loading a large memory data.

** After a year or two, I suddenly encountered this problem, maybe I didn't pay attention to it before.
In fact, if it does not appear frequently, you don't need to pay attention to it. Just click OK. **
The following prompt is displayed:

If this problem occurs, click Yes to restart Eclipse.
If there are any unsaved changes, click No. After checking, restart Eclipse.