Method and device for preventing memory leakage, and computer readable storage medium

Abstract

The invention discloses a method for preventing memory leakage, which comprises the following steps of customizing a static executable object, and realizing a Runnable interface by the static executable object; transmitting at least one first Runnable object to be executed into the static executable object by using a proxy mode to perform weak reference packaging to obtain a packaged second Runnable object; customizing a strong reference queue, and after the first Runnable object is packaged, inserting the first Runnable object into the strong reference queue; submitting the packaged second Runnable object to a thread pool to wait for execution; and when a target thread in the thread pool starts to be executed, deleting a first Runnable object corresponding to a second Runnable object executed by the target thread in the strong reference queue. The invention further provides a device for preventing memory leakage and a computer readable storage medium. According to the memory leakage prevention method provided by the invention, the reference of the Runnable object to the external class can be decoupled, and the memory leakage of the external class is avoided.

Description

technical field [0001] The embodiments of the present invention relate to the technical field of memory performance optimization, and in particular, to a method, device, and computer-readable storage medium for preventing memory leaks. Background technique [0002] In the prior art, Java applications are all based on multi-threading. To use multi-threading, you must define the main Runnable class of the thread. When the main Runnable class used is defined as an internal class, the Runnable object will hold a reference to the external class. . When a thread is submitted to the thread pool for use, it is not guaranteed that the thread will be executed immediately. Even if the thread is executed immediately, it may be because the thread involves time-consuming input / output (I / O) operations, resulting in a time-consuming thread execution. Unsure, in this way, the external class held by the Runnable object cannot be released, resulting in a memory leak of the external class. C...

AI Technical Summary

Problems solved by technology

When a thread is submitted to the thread pool for use, it is not guaranteed that the thread will be executed immediately. Even if the thread is executed immediately, it may be because the thread involves time-consuming input / output (I / O) operations, resulting in a time-consuming thread execution. Unsure, in this way, the external class held by the Runnable object cannot be released, resulting in a memory leak of the external class

Images