Method for checking sofeware memory leak

Abstract

The invention discloses a kind of examining method for software memory leakage. The method confirms the memory block which is applied by the application at first and the occupied time of different memory blocks, when the application runs, it records the applying and releasing information of the memory, and finds the memory block which is not released and exceeds the time, it ascertains the memory leakage point of the application; the examination to the memory leakage of application with the method has little impact on the application, it's easy to be realized and low cost, it applies to the long-term examination for the memory leakage, and helps to find the leakage fault emerged in actual application environment.

Description

technical field [0001] The invention relates to a method for testing software performance, in particular to a method for checking software memory leaks. Background technique [0002] Among the many defects of software (or application program), memory leak is a relatively difficult error to find. There may be various reasons for the software memory leak, for example, it may be caused by software design defects, or it may be caused by the operating system. In any case, if the software has a memory leak defect, it will reduce the available memory of the system and reduce the operating efficiency; for those software that need to run continuously for a long time, even if only a small amount of memory is leaked at a time, the long-term accumulation will lead to system memory loss. Exhausted until paralyzed. Therefore, software memory leak check is an important check item in the test. Currently, software memory leak checks are generally performed using some dedicated memory chec...

AI Technical Summary

Problems solved by technology

However, there are several shortcomings in using these tools: first, most of these tools are large-scale commercial software, and the cost is relatively high; second, these tools implement memory operation monitoring by inserting monitoring codes into executable files, making the software The program code or capacity will increase a lot, and it will run much slower. It can only be used when the software is in the testing stage, that is, it can only be checked statically. It cannot be detected when the software is officially running online, and some hidden memory leaks, It can only appear in the official operating environment. To catch these memory leaks, the methods provided by the above-mentioned dedicated memory checking tools are powerless.

Images