When operating a Linux system, using MyEclipse to start Tomcat suddenly becomes very slow, and a large amount of memory and CPU are occupied. However, this problem did not occur before. So what caused this situation? The editor below will introduce to you the solution to the problem that Linux MyEclipse is too slow to start Tomcat.
In fact, this can be regarded as a bug of MyEclipse. Not surprisingly, the above situation will appear after you add a new breakpoint!
Let’s look at it through diagrams:
There should not be a breakpoint in the red box in the picture above. If you double-click there, the breakpoint will normally appear in the first executable statement of the method (such as the blue box in the picture above, the third breakpoint from top to bottom) ).
Under normal circumstances, we can only set breakpoints on the method signature (as shown in the second breakpoint in the figure above) and the method body. It is impossible to set breakpoints on comments. If MyEclipse allows us to set breakpoints on comments, the above situation will occur! (It is worth mentioning that if the code is not significantly changed, such as copying and pasting from other places, the above situation will generally not occur)
Solution: Remove these breakpoints that should not exist!
But you will soon find out that it doesn’t work. Double-clicking again cannot cancel the breakpoint! (In most cases this is true)
As shown in the picture, you can switch to debugging mode, find the breakpoint and cancel.
Although there are traces of breakpoints, it will not affect anything at this time.
The above is the editor’s summary of the solution to the problem that Linux MyEclipse starts Tomcat too slowly. When you encounter this problem, you only need to remove some extra breakpoints to solve it.
