The eclipse startup parameter solves the issue that CPU usage is 100% and must be "ended immediately ".

Post:

Symptoms:
When using eclipse, you can click a button or icon or even enterCodeTime, the entireProgramWorker occupies CPU 50% (equivalent to a single CPU of 200), memory occupies more than MB, and the CPU and memory usage values remain unchanged. The fan of the machine starts to roar and waits for half a day. Click "close" to bring up the "close now" dialog box. You can only force exit without any help. Sometimes, when you encounter it more than 10 times a day, the availability is basically lost.

Find a solution:
Baidu and Google search. The general solution is to adjust the startup parameter-XMS-xmx to increase the heap memory. However, setting it to-xms512m-xmx512m on the above machine is still ineffective, by the time the response is lost, the memory occupied is still more than 200 MB.
It seems that this problem has to be solved by yourself. Run the following command to start Eclipse:
Java-xms512m-xmx512m-jar startup. Jar
When the response is lost, we find that Java is printed in the command line. lang. outofmemoryerror: permgen space, open workspace /. metadata /. log File, found many such strings, paste this paragraph on the search engine, found many such problems, but generally occurs in Tomcat, Weblogic and other Web applications, no one has reported that it will appear in eclipse. The solution is to add the startup parameters:
-XX: maxnewsize = 256 m-XX: maxpermsize = 256 m
In eclipse. ini, change the startup parameter:

- Xms512m - Xmx512m - XX: maxnewsize = 256 m - XX: maxpermsize = 256

It took a few days to start eclipse and there were no symptoms of losing response.

Or: Java-xms512m-xmx512m-jar startup. Jar