java内存泄漏（JAVA memory leaks）.docVIP

java内存泄漏（JAVA memory leaks） First, the question raised An important advantage of Java is the automatic management of memory recovery through the garbage collector (Garbage, Collection, GC), and the programmer does not need to call the function to free the memory. As a result, many programmers assume that Java does not have a memory leak problem, or that memory leaks are not the responsibility of the program, but rather GC or JVM. In fact, this idea is incorrect, because Java also has memory leaks, but its performance is different from that of C++. As more and more server programs adopt Java technology, such as JSP, Servlet, EJB, server programs often run for long periods of time. In addition, in many embedded systems, the total amount of memory is very limited. Memory leak problems also become critical, even if each time a small amount of leakage is run, after long-term operation, the system is also faced with the risk of collapse. Two how does Java manage memory? To determine whether there is memory leak in Java, we must first understand how Java manages memory. Java memory management is the object allocation and release problem. In Java, the programmer needs to apply memory space for each object through the keyword new (except for the basic type), and all objects allocate space in the heap (Heap). In addition, the release of the object is determined and executed by the GC. In Java, the memory allocation is done by the program, and the memory release is done by GC, and this two line approach really simplifies the programmers work. But at the same time, it adds to the work of JVM. This is also one of the reasons why Java programs are running at a slower rate. Because GC has the right to release objects, GC must monitor the running state of each object, including object applications, references, references, assignments, and so on, and GC needs to be monitored. The object state is monitored to release objects more accurately and in a timely fashion, and the fundamenta