JP5327886B2 - Memory leak determination device, memory leak determination method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To detect a failure of computer resource release early and reduce a risk of erroneous determination on a failure of computer resource release regardless of the magnitude of an increase rate of computer resource usage. <P>SOLUTION: In a memory leak determination device (a resource release failure determination device) 1, a memory usage obtaining unit (a resource usage obtaining unit) 21 obtains memory usage (resource usage) for each process, and a maximum value update counter 22 counts the number of updating the maximum value of the memory usage for every process. A memory leak determination unit (a resource release failure determination unit) 23 determines that a memory leak (a resource release failure) is occurring when the number of updating the maximum value of the memory usage is equal to or greater than a predetermined threshold and the memory usage is equal to or greater than a predetermined threshold. <P>COPYRIGHT: (C)2012,JPO&amp;INPIT

Description

The present invention, main Moririku determination device, a memory leak judgment method, and a program.

A phenomenon in which an operating system (OS) or application software process does not free a dynamically allocated memory area due to a program bug or virus contamination is called a memory leak. When a memory leak occurs, there is a possibility that the usable memory area decreases and the computer processing capacity decreases, or the operation of the computer becomes unstable.
As a method of determining the presence or absence of a memory leak, there is a method of detecting the memory usage amount for each process and determining that there is a memory leak when the memory usage amount of any process exceeds a predetermined threshold. However, in this method, it is not determined that there is a memory leak until the memory usage exceeds the threshold, and detection of the memory leak is delayed. In addition, when no memory leak actually occurs and the memory usage amount only temporarily exceeds the threshold value, it is erroneously detected that there is a memory leak.
Therefore, in Patent Document 1, for each process, a memory usage increase rate is calculated by comparing the memory usage average value for the last 24 hours with the past memory usage average value, and the memory usage of any process A method of determining that there is a memory leak when the increase rate exceeds a predetermined threshold is shown. According to this method, since the presence / absence of a memory leak is determined based on the memory usage increase rate, the memory leak can be detected at an early stage where the memory usage is relatively small.

JP 2005-250751 A

  However, in the method of Patent Document 1, even when a process for securing a relatively large memory area is in an execution state for a certain time or more (for example, the latest 24 hours), the memory usage increase rate may exceed the threshold value. It is done. In this case, there is a risk of erroneously determining that there is a memory leak even though no memory leak actually occurs. Also, with this method, it is not possible to detect a memory leak whose memory usage rate is below a threshold.

  Such a problem may occur not only for memory resources but also for various computer resources. For example, when determining whether or not a process opened file is closed by comparing the number of files opened by the process with a threshold value, or comparing the thread end leakage of a process that performs multithread processing with the thread number and the threshold value. As in the case described above, there is a risk of erroneous determination due to a temporary increase in the number of open files and the number of threads.

The present invention has been made in consideration of such circumstances, and its purpose is to detect computer resource release omissions at an early stage, and to release computer resources regardless of the rate of increase in computer resource usage. fear of small Ime Moririku determination device performs erroneous determination of leak presence is to provide a memory leak judgment method, and a program.

The present invention has been made to solve the problems described above, a memory leak determination device according to an aspect of the present invention, the process is a memory leakage determination unit determines the presence or absence of memory leaks using memory, the and memory usage acquisition unit for acquiring the memory usage of the process, the maximum value update count counting section for counting the maximum number of updates of the memory usage the memory usage acquisition unit acquires the maximum value update count counting A memory leak determination unit that determines the presence or absence of the memory leak based on the maximum number of update times counted by the unit, and the memory leak determination unit obtains the memory usage after a lapse of a certain time from process startup. The maximum value update count is a predetermined number of times, using a value obtained by multiplying a memory constant initial value, which is the memory usage initially acquired by the unit, by a predetermined constant. Becomes higher, and, if the memory usage is equal to or greater than the threshold value, and wherein the determining that there is the memory leak.

A resource release leak determination method according to an aspect of the present invention is a memory leak determination method of a memory leak determination apparatus that determines whether or not a memory leak occurs when a process uses memory, and the memory usage acquisition unit includes: and memory usage acquiring the memory usage of the process, the maximum value update count counting section, the maximum value update count counting to count the maximum number of updates of the memory usage the memory usage acquisition unit acquires a step, a memory leak determination unit, based on the maximum value update number of times the maximum value updating count counting section counts, anda memory leakage determination step of determining whether the memory leak, the memory leak determination In the step, the memory leak determination unit is configured so that the memory usage acquisition unit acquires the first time after a predetermined time has elapsed since the process startup. When a value obtained by multiplying a memory usage initial value that is a memory usage by a predetermined constant is a threshold, the maximum value update count is greater than or equal to a predetermined count, and the memory usage is equal to or greater than the threshold, It is determined that there is a memory leak .

The program according to an aspect of the present invention causes a computer as a memory leak determining device determines the presence or absence of memory leaks when the process uses memory, and memory usage acquiring the memory usage of the process , the maximum value update count counting step for counting the maximum number of updates of the memory usage of acquired by the memory usage acquisition step, on the basis of the maximum value update count for counting at the maximum value updating number counting step the memory leakage determination step of determining whether a memory leak, is executed, the in memory leakage determination step, the memory use amount initial value is the memory usage acquired first after the elapse from the process starts a predetermined time With the value multiplied by a predetermined constant as a threshold value, the maximum value update count is greater than the predetermined count, , If the memory usage is equal to or greater than the threshold value, a program for determining that there is the memory leak.

  According to the present invention, it is possible to detect a computer resource release omission early and to reduce the possibility of erroneous determination of the presence or absence of a computer resource release regardless of the magnitude of the increase rate of the computer resource usage.

It is a block diagram which shows schematic structure of the memory leak determination apparatus in one Embodiment of this invention. In the same embodiment, it is a figure which shows the example of the process information which the process information storage part 311 memorize | stores. 5 is a diagram illustrating an example of memory usage information stored in a memory usage information storage unit 312 in the embodiment. FIG. 4 is a diagram illustrating an example of determination condition information stored in a determination condition information storage unit 313 in the embodiment. FIG. In the same embodiment, it is a figure which shows the example of the process content information which the process content information storage part 314 memorize | stores. In the same embodiment, it is a figure which shows the example of the process result information which the process result information storage part 315 memorize | stores. In the embodiment, the memory leak determination unit 23 is a graph showing an example of determining that there is a memory leak. 4 is a graph illustrating a first example in which the memory leak determination unit determines that there is no memory leak in the embodiment. In the embodiment, the memory leak determination unit is a graph showing a second example of determining that there is no memory leak. In the embodiment, the memory leak determination unit is a graph showing a third example of determining that there is no memory leak. FIG. 6 is a diagram illustrating a processing procedure for determining whether there is a memory leak, which is performed by the memory leak determination apparatus 1 regarding a certain process in the embodiment. It is a block diagram which shows schematic structure of the file leak determination apparatus in the 1st modification of this invention. It is a block diagram which shows schematic structure of the thread leak determination apparatus in the 2nd modification of this invention.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a configuration diagram showing a schematic configuration of a memory leak determination apparatus according to an embodiment of the present invention. In the figure, a memory leak determination device (resource release leak determination device) 1 includes an operation input unit 11, a display unit 12, a memory usage acquisition unit (computer resource usage acquisition unit) 21, and a maximum value update count. Unit 22, memory leak determination unit (release leak determination unit) 23, countermeasure processing execution unit 24, and storage unit 31. The storage unit 31 includes a process information storage unit 311, a memory usage information storage unit 312, a determination condition information storage unit 313, a processing content information storage unit 314, and a processing result information storage unit 315.

The memory leak determination apparatus 1 determines the presence or absence of a memory leak based on the memory usage of a process on the computer.
The storage unit 31 is realized on a storage area of a computer subject to memory leak determination (hereinafter simply referred to as “computer”), and stores various types of information. The process information storage unit 311 stores process information, which is information used by the memory leak determination apparatus 1 for acquiring the memory usage of each process, for each process.
FIG. 2 is a diagram illustrating an example of process information stored in the process information storage unit 311. In the example shown in the figure, the process information includes “process ID” that is an identification number of the process, “process name” of the process, “execution start time” of the process, and the memory leak determination device 1 The “next time” that is the time to acquire the memory usage of the process is included.

The memory usage information storage unit 312 stores memory usage information, which is information related to the memory usage of the process being executed, for each process.
FIG. 3 is a diagram illustrating an example of memory usage information stored in the memory usage information storage unit 312. In the example of the figure, the memory usage information includes the above-mentioned “process ID” and “process name”, “initial value”, “maximum value” and “current value” of the memory usage of the process, A “maximum value update count” indicating the number of times the maximum value has been updated and a “memory usage threshold” that is a threshold used when the memory leak determination apparatus 1 determines a memory leak are included.

The determination condition information storage unit 313 stores a threshold value and a threshold value calculation reference when the memory leak determination device 1 determines a memory leak.
FIG. 4 is a diagram illustrating an example of determination condition information stored in the determination condition information storage unit 313. In the example of the figure, the determination condition information includes an “update count threshold” that is a threshold for the update count of the memory usage maximum value, and a “memory usage threshold calculation coefficient” that is a calculation criterion for the threshold of the memory usage. In addition, a “determination time interval”, which is a time interval in which the memory leak determination apparatus 1 determines whether or not there is a memory leak, is included. The update count threshold value, the memory usage threshold value calculation coefficient, and the determination time interval are written in the determination condition information storage unit 313, for example, by the operation input unit 11 that has received a user operation.

The processing content information storage unit 314 stores the processing content for the process determined to have a memory leak.
FIG. 5 is a diagram illustrating an example of the processing content information stored in the processing content information storage unit 314. As shown in the example of the figure, the processing content information includes a “processing item name” of processing performed on the process determined to have a memory leak, an “execution command” for executing the processing, A “selection flag” indicating whether or not to perform processing is included. As the process item name, “process stop” to stop (KILL) the process determined to have a memory leak, “script execution” to execute a predetermined script, and information related to memory leak are output to the log "Log output" to be performed, and "Warning display" to warn the user (computer administrator) that a memory leak has occurred. In the execution command column, a command for executing the processing is stored. Further, “◯” in the selection flag indicates that the process is performed, and “×” indicates that the process is not performed. The value of the selection flag is written in the processing content information storage unit 314 by the operation input unit 11 that has received the user's input operation, for example.

The processing result information storage unit 315 stores a processing result for a process determined to have a memory leak.
FIG. 6 is a diagram illustrating an example of the processing result information stored in the processing result information storage unit 315. In the example of the figure, the processing result information includes “determination time” at which the memory leak determination device determines that there is a memory leak, “process ID” and “process name” of the process determined to have memory leak, A “processing item name” for the process and a “processing result” that is a record of the result of the processing are included.

The memory usage acquisition unit 21 acquires the memory usage of each process being executed and writes it in the current value column of the memory usage information storage unit 312. For example, when the determination time interval for the presence / absence of memory leak is set to 5 minutes, the memory usage acquisition unit 21 acquires the memory usage based on the next time stored in the process information storage unit 311 and promptly after acquisition By adding 5 minutes to the next time, the memory usage is acquired every 5 minutes for each process being executed.
The maximum value update count counting unit 22 determines whether or not the memory usage acquired by the memory usage acquisition unit is the maximum value. If it is determined to be the maximum value, the memory usage stored in the memory usage information storage unit 312 is determined. Rewrite the maximum value and the maximum value update count.

The memory leak determination unit 23 determines whether or not there is a memory leak, whether or not the maximum number of updates of the memory usage of the process is equal to or greater than an update count threshold and the current value of the memory usage is equal to or greater than the memory usage threshold. Based on the above, the presence or absence of a memory leak is determined.
The countermeasure processing execution unit 24 performs countermeasure processing based on the processing content information stored in the processing content information storage unit 314 when the memory leak determination unit 23 determines that there is a memory leak.

The operation input unit 11 includes a keyboard, a mouse, and the like, and accepts user input operations. When the operation input unit 11 receives an input of the update count threshold value or the memory usage threshold value calculation coefficient, the operation input unit 11 writes in the corresponding field of the determination condition information storage unit 313, and receives an input of the value of the selection flag, the processing content information storage unit 314 Is written in the corresponding column of the selection flag stored.
The display unit 12 includes a display screen such as a liquid crystal display, and displays a warning when a memory leak occurs. Specifically, when the warning display selection flag is “◯”, the image data of the warning screen is output from the countermeasure processing execution unit 24 to the display unit 12 when a memory leak occurs. The display unit 12 displays a warning screen indicating that a memory leak has occurred based on the image data output from the countermeasure processing execution unit 24.

Note that the memory leak determination apparatus 1 may be realized in a computer that is a memory leak determination target, or may be realized as an apparatus independent of the computer.
When the memory leak determination device 1 is realized in a memory leak determination target computer, for example, a memory usage amount acquisition unit 21, a maximum value update count counter 22, a memory leak determination unit 23, and a countermeasure processing execution unit 24 Is realized as a process on a central processing unit (CPU) of the computer, and each unit of the storage unit 31 is realized by securing a storage area on the storage device of the computer.

  When the memory leak determination apparatus 1 is realized as an apparatus independent of the memory leak determination target computer, the memory leak determination apparatus 1 communicates with the memory leak determination target computer and stores the memory of each process being executed on the computer. Get usage. If it is determined that there is a memory leak, a signal instructing execution of countermeasure processing is transmitted to the computer. The memory leak determination device 1 may be realized on another computer, or may be realized as a dedicated hardware device by a dedicated arithmetic circuit or the like.

Next, the determination of the presence or absence of a memory leak performed by the memory leak determination unit 23 will be described with reference to FIGS.
FIG. 7 is a graph illustrating an example in which the memory leak determination unit 23 determines that there is a memory leak, and shows a change in memory usage of a certain process acquired by the memory usage acquisition unit 21. The vertical axis in the figure indicates the memory size. In addition, the horizontal axis of the figure is the time axis, and indicates the time since the process started. Points P101 to P110 indicate the memory usage of the process acquired by the memory usage acquisition unit 21 at each time. THR is a memory usage threshold value, and indicates a value obtained by multiplying the memory usage value VP at the point P101 at the time of initial acquisition of the memory usage value by the memory usage threshold value calculation coefficient stored in the determination condition information storage unit 313.

The memory leak determination unit 23 refers to the memory usage information in the memory usage information storage unit 312 to determine whether the current value of the memory usage is equal to or greater than the memory usage threshold and the memory usage maximum value update count It is determined that there is a memory leak when it is equal to or greater than the update count threshold stored in the condition information storage unit 313. Hereinafter, in the example illustrated in FIGS. 7 to 10, the update count threshold is set to “8”.
In the example of FIG. 7, at the point P109 and the point P110, the current value of the memory usage is equal to or greater than the memory usage threshold THR. Further, the maximum value update count counter 22 writes the maximum value update count as “0” in the maximum value update count column of the memory usage information storage unit 312 at the point P101 when the memory usage is initially acquired. Thereafter, each time the maximum value is updated, 1 is added to the maximum value update count, such as “1” at the point P102 and “2” at the point P103, and the memory usage information storage unit 312 Write in the maximum update count column. In the case of FIG. 7, since the maximum value is not updated at the point P106, the maximum value update count reaches the update count threshold “8” at the point P110.

  When a memory leak occurs in a process, the memory leaking area of the memory area secured by the process is not released, so the memory usage of the process increases with time as shown in FIG. It is thought to go. Therefore, the memory leak determination unit 23 sets one of the memory leak determination conditions that the maximum value update count of the memory usage is equal to or greater than the update count threshold. On the other hand, if the memory usage increases during normal operation of the process, the memory area secured by the process is released after the processing is completed, so that the memory usage of the process falls within a certain range, that is, a certain value It can be expected that it will not be more. Accordingly, the memory leak determination unit 23 is configured to reduce the erroneous determination that there is a memory leak due to the gradual increase of the memory usage during normal operation of the process, when the current value of the memory usage is equal to or less than the memory usage threshold THR. Determines that there is no memory leak regardless of whether or not the maximum memory usage update count is equal to or greater than the update count threshold.

Note that the memory leak determination unit 23 may determine the presence or absence of a memory leak only by comparing the number of updates of the memory usage maximum value with the update count threshold. In this case, when the maximum number of updates of the memory usage exceeds the update count threshold, the memory leak determination unit 23 determines that there is a memory leak regardless of the current value of the memory usage. Can be detected.
On the other hand, as described above, in addition to the update count of the memory usage maximum value being equal to or greater than the update count threshold, the determination that the current value of the memory usage is equal to or greater than the memory usage threshold THR The possibility of erroneous determination that there is a memory leak can be reduced by gradually increasing the memory usage during normal operation.

It should be noted that immediately after the process is activated, the process has not yet secured a memory area, and the memory usage may be extremely small. For this reason, when the memory usage acquisition unit 21 acquires the memory usage immediately after starting the process as the initial acquisition value of the memory usage, and calculates the memory usage threshold THR based on this value, the memory usage threshold THR The value becomes extremely small, and there is a possibility that the erroneous determination that there is a memory leak cannot be reduced due to the gradual increase of the memory usage amount in the normal operation of the process described above. Therefore, the memory usage acquisition unit 21 acquires the first memory usage at a point P101 after a predetermined time has elapsed since the process activation.
If the process is programmed to reserve a memory area immediately upon startup, the memory usage acquisition unit 21 may acquire the initial memory usage when the process is started. As a result, the memory usage acquisition unit 21 can detect a memory leak at an earlier stage than when the memory usage acquisition is performed for the first time after a predetermined time has elapsed since the process activation.

  FIG. 8 is a graph illustrating a first example in which the memory leak determination unit determines that there is no memory leak, and illustrates an example in which the memory usage of the process temporarily exceeds the memory usage threshold. As in FIG. 7, the vertical axis of FIG. 8 indicates the memory size, and the horizontal axis indicates the time since the process was started. Points P201 to P210 indicate the memory usage of the process acquired by the memory usage acquisition unit 21 at each time. THR indicates a memory usage threshold.

  The memory usage of the process displayed in the graph is equal to or greater than the memory usage threshold value THR at the point P202, but the maximum memory usage update count at this point is “1”, and the update frequency threshold “ Since it is less than 8 ”, the memory leak determination unit 23 determines that there is no memory leak. Further, since the memory usage at the points P203 to P210 is equal to or less than the memory usage at the point P202, the maximum number of times the memory usage is updated remains “1”. For this reason, the memory leak determination unit 23 also determines that there is no memory leak at the point P201 and the points P203 to P210 including the point P201 where the maximum value of the memory usage amount is “0”. Note that at the point P201 and the points P203 to 210, the current value of the memory usage is less than the memory usage threshold THR, so the memory leak determination unit 23 determines that there is no memory leak.

  As described above, the memory leak determination unit 23 determines the presence / absence of a memory leak based on the maximum number of times the memory usage is updated. Therefore, the memory leak is determined only by comparing the memory usage with the memory usage threshold. Unlike the method, when the memory usage that increases or decreases in the normal operation of the process temporarily exceeds the memory usage threshold, it is possible to reduce the possibility of erroneously determining that there is a memory leak.

  FIG. 9 is a graph illustrating a second example in which the memory leak determination unit determines that there is no memory leak, and illustrates an example in which a process periodically secures a certain memory area. As in FIGS. 7 to 8, the vertical axis in FIG. 9 indicates the memory size, and the horizontal axis indicates the time since the process was started. Points P301 to P310 indicate the memory usage of the process acquired by the memory usage acquisition unit 21 at each time. THR indicates a memory usage threshold.

  The memory usage of the process displayed in the graph is equal to or greater than the memory usage threshold THR at the point P302, but the maximum memory usage update count at this point is “1”, and the update count threshold “ Since it is less than 8 ”, the memory leak determination unit 23 determines that there is no memory leak. In addition, the memory usage at the points P306 and P309 is the same as the memory usage at the point P303, and the maximum number of times the memory usage is updated at points P304 to P310 remains “1”. For this reason, the memory leak determination unit 23 also determines that there is no memory leak in the points P301 to P302 and the points P304 to P310, including the points P301 to P302 where the maximum number of times of updating the memory usage is “0”. At points P301, P302, P304, P305, P307, P308, and P310, the memory leak determination unit 23 determines that there is no memory leak because the current value of the memory usage is less than the memory usage threshold THR. To do.

  As described above, the memory leak determination unit 23 determines the presence / absence of a memory leak based on the maximum number of times the memory usage is updated. Therefore, the memory leak is determined only by comparing the memory usage with the memory usage threshold. Unlike the method, it is possible to reduce the possibility of erroneously determining that there is a memory leak even when the memory usage that increases or decreases in the normal operation of the process regularly exceeds the memory usage threshold.

  FIG. 10 is a graph illustrating a third example in which the memory leak determination unit determines that there is no memory leak, and illustrates an example in which the memory usage of the process changes within a range less than the memory usage threshold. Similar to FIGS. 7 to 9, the vertical axis in FIG. 10 indicates the memory size, and the horizontal axis indicates the time since the process was started. Points P401 to P410 indicate the memory usage of the process acquired by the memory usage acquisition unit 21 at each time. THR indicates a memory usage threshold.

  In the example of the figure, the maximum value of the memory usage is updated at points P402 to P409, and the maximum value update count is “8” at the point 409, which is the same as the update count threshold value. However, since the current value of the point P409 is smaller than the determination threshold value THR, the memory leak determination unit 23 determines that there is no memory leak at the point P409. Also, at points P401 to P408 and P410, the memory usage is less than the memory usage threshold, and the memory leak determination unit 23 determines that there is no memory leak. At points P401 to P408, the maximum memory usage update count is less than the update count threshold “8”. In this respect as well, the memory leak determination unit 23 determines that there is no memory leak.

  When the memory usage increases in the normal operation of the process, it is expected that the memory usage will decrease as the memory area secured by the process is released after the processing is completed, for example, as indicated by a point P410 in FIG. it can. Thereby, it can be expected that the memory usage of the process falls within a certain range, that is, not more than a certain value. Therefore, as described above, the memory leak determination unit 23 determines that the current value of the memory usage is the memory usage threshold value in order to reduce the erroneous determination that there is a memory leak due to the gradual increase of the memory usage during the normal operation of the process. One of the memory leak determination conditions is THR or more.

Next, the operation of the memory leak determination apparatus 1 will be described with reference to FIG.
FIG. 11 is a diagram showing a procedure for determining whether or not there is a memory leak, which the memory leak determination apparatus 1 performs regarding a certain process. When a new process is executed, the memory leak determination apparatus 1 starts the process shown in FIG. In the following, the process for determining whether or not there is a memory leak is referred to as “target process” in FIG.
When the target process is newly executed, for example, an OS (Operating System) outputs the process ID, process name, and execution start time of the target process to the memory usage acquisition unit 21. The memory usage acquisition unit 21 associates the process ID, process name, and execution start time output from the OS, and adds them to the process information stored in the process information storage unit 311. In addition, the memory usage acquisition unit 21 associates the process ID output from the OS with the process name and adds it to the memory usage information stored in the memory usage information storage unit 312 (step S101).

Thereafter, the memory usage acquisition unit 21 waits for a predetermined time (step S102) and acquires the memory usage of the target process (step S103).
As described above, waiting for the elapse of the predetermined time prevents the memory usage threshold value THR from being calculated based on an extremely small memory usage amount in a state where the target process has not yet secured the memory area. Because. The waiting time in step S102 may be the same as the determination time interval stored in the determination condition information storage unit 313, or may be a time determined separately from the determination time interval. For example, the user takes statistics of memory usage for each time during normal operation of the process, and determines the waiting time and memory usage threshold value calculation coefficient in step S102 based on the statistics, thereby determining the condition information storage unit 313. You may make it write in.
The memory usage acquisition unit 21 receives, for example, the process ID, process name, and memory usage of each process being executed from the OS as needed, and the memory usage output from the OS when a predetermined time elapses in step S102. Let the amount be the memory usage acquisition value.

  The memory usage acquisition unit 21 writes the acquired memory usage in the initial value column, maximum value column, and current value column of the target process row of the memory usage information stored in the memory usage information storage unit 312. . The memory usage acquisition unit 21 reads out the memory usage threshold value calculation coefficient from the determination condition information storage unit 313, and multiplies the read memory usage threshold value calculation coefficient by the previously acquired memory usage amount, thereby increasing the memory usage. An amount threshold is calculated. The memory usage acquisition unit 21 writes the calculated memory usage threshold in the memory usage threshold column of the target process row of the memory usage information. Further, the memory usage acquisition unit 21 writes “0” in the maximum value update count column of the row of the target process of the memory usage information. In addition, the memory usage acquisition unit 21 reads the determination time interval from the determination condition information storage unit 313, and adds the read determination time interval to the time when the memory usage is acquired in step S103, so that the memory of the target process is obtained. The next time for determining whether there is a leak is calculated. The memory usage acquisition unit 21 writes the calculated time in the next time column of the process line of the process information (step S104).

  Then, the memory usage acquisition unit 21 waits for the elapse of time until the time written at the next time is reached (step S105). Thereafter, the memory usage acquisition unit 21 determines whether the target process is being executed. For example, the memory usage acquisition unit 21 determines that the target process is being executed when the process ID and process name of the target process are included in the information of the process being executed that is output as needed from the OS. To do. On the other hand, when the process ID and the process name of the target process are not included, the memory usage acquisition unit 21 determines that the target process is not being executed (step S106). If it is determined that the target process is not being executed (step S106: NO), the memory usage acquisition unit 21 deletes the row of the target process from the process information and the memory usage information (step S121). Then, the process of FIG. 11 is complete | finished.

On the other hand, when it is determined in step S106 that the target process is being executed (step S106: YES), the memory usage acquisition unit 21 acquires the memory usage of the target process (step S107), and the memory usage information The current value of the memory usage of the target process stored in the storage unit 312 is updated to the acquired memory usage.
In addition, the memory usage acquisition unit 21 reads the next time from the process information stored in the process information storage unit 311. As described above, the next time is information indicating the time when the memory leak determination device 1 (the memory leak determination unit 23) next determines the memory leak of the target process. Further, the memory usage acquisition unit 21 reads the determination time interval from the determination condition information stored in the determination condition information storage unit 313. The memory usage acquisition unit 21 calculates a new next time by adding a determination time interval to the read next time, and updates the next time of the target process stored in the process information storage unit 311 to the calculated next time. .

  Thereafter, the memory usage acquisition unit 21 outputs a signal indicating that the current value of the memory usage has been updated to the maximum value update count counter 22. For example, the memory usage acquisition unit 21 outputs a signal indicating that the memory usage current value has been updated, including the process ID of the target process. Thereby, the maximum value update number counting unit 22 can grasp which process is the target process (step S108).

When receiving the output of the signal indicating that the current value of the memory usage is updated, the maximum value update count counting unit 22 obtains the current value and the maximum value of the memory usage of the target process from the memory usage information storage unit 312. read out. Then, the maximum value update count counter 22 determines whether or not the maximum value has been updated, that is, whether or not the read current value is greater than the maximum value (step S109). When it is determined that the maximum value has been updated (step S109: YES), the maximum value update count counter 22 stores the target process in the maximum value column of the memory usage of the target process stored in the memory usage information storage unit 312. Write the current value of memory usage for. In addition, the maximum value update count counter 22 updates the maximum value update count of the memory usage of the target process stored in the memory usage information storage 312 to a value obtained by adding 1 to the maximum update count.
Thereafter, the maximum value update count counter 22 outputs (transfers) a signal output from the memory usage acquisition unit 21 and indicating that the current value of the memory usage has been updated to the memory leak determination unit 23 (above). Step S110).

When receiving a signal indicating that the current value of the memory usage has been updated, the memory leak determination unit 23 determines whether there is a memory leak related to the target process. As described above, the memory leak determination unit 23 reads the current value M of the memory usage of the target process, the maximum value update count U, and the memory usage threshold T _M from the memory usage information storage unit 312. from the determination condition information storage unit 313, reads the number of updates threshold _{T U.} The memory leak determination unit 23 determines that there is a memory leak with respect to the target process when Expression (1) is satisfied, and determines that there is no memory leak with respect to the target process when the expression (1) is not satisfied (step S111).
M ≧ T _M and U ≧ T _U Formula (1)

If it is determined that there is a memory leak (step S111: YES), the memory leak determination unit 23 includes the process ID of the target process in a signal instructing execution of the countermeasure process, and outputs the signal to the countermeasure process execution unit 24.
When the countermeasure processing execution unit 24 receives an output of a signal instructing execution of the countermeasure processing, the countermeasure processing executing unit 24 executes countermeasure processing for the memory leak. Specifically, the countermeasure process execution unit 24 reads the process ID of the target process from the signal instructing execution of the countermeasure process, and the process whose selection flag is “◯” from the process content information storage unit 314. Read the execution command. Then, the countermeasure processing execution unit 24 executes the read execution command for the target process indicated by the read process ID (step S112). Thereafter, the process returns to step S105.

On the other hand, if it is determined in step S109 that the maximum value has not been updated (step S109: NO), the process proceeds to step S111. That is, the process proceeds to the determination of the presence or absence of memory leak without updating the maximum value and the maximum value update count.
If it is determined in step S111 that there is no memory leak (step S111: NO), the process returns to step S105. That is, the next time arrival is awaited without taking measures against the memory leak.

As described above, the memory leak determination unit 23 of the memory leak determination apparatus 1 determines the presence or absence of a memory leak based on whether or not the maximum value update count of the memory usage of the target process is equal to or greater than the maximum value update count threshold. Therefore, when compared with a memory leak determination device that determines whether or not a memory leak is present only by whether or not the memory usage of the process is equal to or greater than a threshold, the memory leak determination device 1 is earlier in the memory usage than the threshold. A memory leak can be detected. In this respect, the memory leak determination apparatus 1 can detect the occurrence of the memory leak at an early stage.
In addition, when no memory leak actually occurs and the memory usage of the target process is merely increased temporarily, the memory leak determination apparatus 1 sets the maximum number of times of update of the memory usage of the target process. Based on this, it can be determined that there is no memory leak.

Also, even if the memory usage increase rate is a large value, such as when a process that secures a relatively large memory area has been in a running state for a certain period of time, the memory usage is constant if no memory leak has occurred. It can be expected that the maximum update count of the memory usage will not exceed the maximum update count threshold. In this case, the memory leak determination apparatus 1 can determine that there is no memory leak. In this respect, the memory leak determination apparatus 1 is less likely to make an erroneous determination regarding the presence or absence of a memory leak regardless of the size of the memory usage increase rate.
Furthermore, when a memory leak occurs, it is conceivable that the memory usage continues to increase regardless of the increase rate of the memory usage. Even when the increase rate of the memory usage is small, the memory leak detection device 1 does not change the memory usage when the maximum memory usage update count is equal to or greater than the update count threshold and the memory usage is equal to or greater than the memory usage threshold. It can be determined that there is a memory leak by detecting that the usage amount continues to increase. In this respect as well, the memory leak determination apparatus 1 is less likely to make an erroneous determination as to whether or not there is a memory leak regardless of the amount of increase in memory usage.

Further, the memory leak determination unit 23 determines whether the current value of the memory usage of the target process is equal to or greater than the memory usage threshold, in addition to whether or not the maximum update count of the memory usage of the target process is equal to or greater than the maximum value update count threshold. The presence or absence of a memory leak is determined based on whether or not. As a result, when a memory leak does not occur and the memory usage of the target process falls within a certain range, it is possible to reduce an erroneous determination that there is a memory leak by gradually increasing the memory usage during normal operation of the process.
In addition, the memory leak determination apparatus 1 is erroneous even if the memory usage threshold value is set to a small value, as compared with the memory leak determination apparatus that determines the presence or absence of a memory leak only by determining whether the memory usage amount of the process is equal to or greater than the threshold value. The possibility of determination can be reduced. Because even if the memory usage of the target process temporarily or periodically exceeds the memory usage threshold, it is determined whether the maximum update count of the memory usage of the target process is equal to or higher than the maximum update count threshold. This is because it is possible to reduce the possibility of erroneous determination that there is a memory leak even though no memory leak has occurred.
Therefore, it is possible to detect a memory leak at a stage where the memory usage of the target process is small, that is, earlier than a memory leak determination device that determines whether or not a memory leak exists based on whether or not the memory usage of the process is equal to or greater than a threshold. .

  Further, in the memory leak determination device 1, the memory usage amount acquisition unit 21 calculates a value obtained by multiplying the initial value of the memory usage amount by the memory usage threshold calculation coefficient, that is, a value obtained by multiplying the initial value of the memory usage amount by a predetermined constant. The memory usage threshold is used, and the memory leak determination unit 23 determines the presence or absence of a memory leak using the memory usage threshold. As described above, the memory leak determination unit 23 determines the presence / absence of a memory leak by using the memory usage threshold set according to the scale of the determination target process, so that it can be expected that the presence / absence of the memory leak can be determined more accurately. .

Note that the memory leak determination unit 23 may collectively determine the presence or absence of a memory leak for a plurality of processes. For example, the memory usage acquisition unit 21 acquires the memory usage for all the processes being executed, and calculates a memory usage average value obtained by dividing the memory usage of all the processes being executed by the number of processes being executed. The memory leak determination unit 23 has a memory usage average value calculated by the memory usage acquisition unit 21, the maximum update count of the memory usage average value is equal to or greater than an update count threshold, and the memory usage average value is a memory It is determined that there is a memory leak when the usage average value threshold is exceeded.
Thus, by determining whether or not there is a memory leak for a plurality of processes, it is not necessary to store memory usage information or the like for each process, so that the memory capacity used for memory leak determination can be reduced.

  Note that the memory usage threshold used by the memory leak determination unit 23 to determine whether there is a memory leak is not limited to the above-described initial value of the memory usage. For example, a memory usage threshold value may be determined in advance according to the type of process. Thereby, it is possible to reduce the load for the memory usage amount obtaining unit to calculate the memory usage threshold value.

<First Modification>
Although the case where the presence / absence of a memory leak is determined has been described above, the present invention can also be applied to the determination of the presence / absence of a close of a file opened by a process (hereinafter referred to as “file leak”).
When a file leak occurs, a memory leak occurs because the memory area of the file that has been closed is not released. In addition, when there is a process waiting for the release of a file that has been closed, the process does not acquire the file, which may cause a reduction in the processing speed of the process, and instability of the computer.

FIG. 12 is a block diagram showing a schematic configuration of the file leak determination apparatus in the first modification of the present invention. In the figure, a file leak determination device (computer resource release leak determination device) 4 includes an operation input unit 11, a display unit 12, an open file number acquisition unit (computer resource usage acquisition unit) 51, and a maximum value update count. A counting unit 52, a file leak determination unit (release leak determination unit) 53, a countermeasure processing execution unit 24, and a storage unit 61 are provided. The storage unit 61 includes a process information storage unit 311, an open file number information storage unit 612, a determination condition information storage unit 613, a processing content information storage unit 314, and a processing result information storage unit 315.
In the figure, the same reference numerals (11, 12, 24, 311, 314, 315) are given to the portions having the same functions as those in FIG.

The open file number information storage unit 612 replaces the initial value, maximum value, and current value of the memory usage of each process being executed with the initial value, maximum value, and current value of the number of open files of each process being executed. And a memory usage amount information storage unit 312 of FIG. 1 in that an open file number threshold value (determination threshold value for the current value of the open file number) is stored instead of the memory usage amount threshold value.
The determination condition information storage unit 613 is different from the determination condition information storage unit 313 of FIG. 1 in that it stores an open file number threshold calculation coefficient instead of the memory usage threshold calculation coefficient. The open file number threshold calculation coefficient is a coefficient for calculating the open file number threshold stored in the open file number information storage unit 612 by multiplying the open file number initial value stored in the open file number information storage unit 612. is there.

The open file number acquisition unit 51 acquires the number of open files of each process being executed from the OS, and displays the open file number information including the initial value, current value, and open file number threshold of the number of open files of each process. At the point of writing to the number information storage unit 612, the memory usage of each process being executed is acquired from the OS, and the memory usage information including the initial value, current value, and memory usage threshold of the memory usage of each process is obtained. This is different from the memory usage acquisition unit 21 of FIG. 1 that writes to the memory usage information storage unit 312.
The maximum value update number counting unit 52 determines whether or not the maximum value of the number of open files has been updated. If it is determined that the maximum value has been updated, the maximum number of open files stored in the open file number information storage unit 612 is determined. It is determined whether the maximum value of the memory usage has been updated in terms of updating the maximum value update count. If it is determined that the maximum value has been updated, the memory usage information storage unit 312 stores the memory usage This is different from the maximum value update count counter 22 in FIG. 1 that updates the maximum value and the maximum value update count.
The file leak determination unit 53 reads the current value of the open file number, the maximum value update count, and the open file count threshold value from the open file number information storage unit 612, and reads the update count threshold value from the determination condition information storage unit 613 to obtain the maximum When the value update count threshold is equal to or greater than the update count threshold and the current value of the number of open files is equal to or greater than the open file count threshold, it is determined from the memory usage information storage unit 312 that there is a file leak. Current value, maximum value update count, and memory usage threshold value are read, the update count threshold value is read from the determination condition information storage unit 313, the maximum value update count threshold value is equal to or greater than the update count threshold value, and the memory usage amount Unlike the memory leak determination unit 23 in FIG. 1 that determines that there is a memory leak when the current value is equal to or greater than the memory usage threshold. That.

Since the file leak determination device 4 determines the presence / absence of a file leak based on the maximum number of updates of the number of open files, a file leak determination device that determines whether there is a file leak based only on whether the number of open files is equal to or greater than a threshold value In comparison, a file leak can be detected at an earlier stage where the number of open files is less than the threshold.
If no file leak actually occurs and the number of open files of the file leak determination target process (hereinafter referred to as “target process”) has only increased temporarily, the file leak determination apparatus 4 Based on the maximum number of updates of the number of open files of the target process, it can be determined that there is no file leak.

Also, even if the increase rate of the number of open files is large, such as when a process that uses a large number of files has been in a running state for a certain period of time, if there is no file leak, the number of open files is within a certain range. It can be expected that the maximum update count of the number of open files will not exceed the maximum update count threshold. In this case, the file leak determination device 4 can determine that there is no file leak. In this respect, the file leak determination apparatus 1 is less likely to make an erroneous determination regarding the presence or absence of a file leak regardless of the increase rate of the number of open files.
Furthermore, if a file leak occurs, the number of open files may continue to increase regardless of the increase rate of the number of open files. Even when the rate of increase in the number of open files is small, the file leak detection device 4 opens when the maximum number of open file updates exceeds the update count threshold and the number of open files exceeds the open file count threshold. By detecting that the number of files continues to increase, it can be determined that there is a file leak. Also in this respect, the file leak determination device 4 is less likely to make an erroneous determination as to whether or not there is a file leak regardless of the increase rate of the number of open files.

Further, the file leak determination unit 53 determines whether the current value of the number of open files of the target process is equal to or greater than the threshold of open files, in addition to whether or not the maximum value of the number of open files of the target process is equal to or greater than the maximum value update count threshold. Whether or not there is a file leak is determined based on whether or not the file leaks. Thereby, when there is no file leak and the number of open files of the target process falls within a certain range, it is possible to reduce erroneous determination that there is a file leak by gradually increasing the number of open files in the normal operation of the process.
In addition, the file leak determination device 4 is erroneous even if the open file number threshold is set to a small value as compared with the file leak determination device that determines whether or not there is a file leak only by whether or not the number of open files in the process is equal to or greater than the threshold. The possibility of determination can be reduced. Because, even when the number of open files in the target process temporarily or periodically exceeds the open file count threshold, it is determined whether the maximum update count of the target process open file count is equal to or greater than the maximum update count threshold. This is because the possibility of erroneous determination that there is a file leak even though no file leak has occurred can be reduced.
Therefore, it is possible to detect a file leak at a stage where the number of open files of the target process is small, that is, earlier than a file leak determination device that determines whether there is a file leak only by determining whether the number of open files in the process is equal to or greater than a threshold. .

  In the file leak determination device 4, the open file number acquisition unit 51 calculates a value obtained by multiplying an initial value of the number of open files by an open file number threshold value calculation coefficient, that is, a value obtained by multiplying the initial value of the number of open files by a predetermined constant. The open file count threshold is used, and the file leak determination unit 53 determines whether there is a file leak using the open file count threshold. As described above, the file leak determination unit 53 determines the presence / absence of a file leak using the open file number threshold set in accordance with the scale of the process to be determined, so it can be expected that the file leak presence / absence can be determined more accurately.

<Second Modification>
The present invention can also be applied to determining whether or not there is a thread end leak (hereinafter referred to as “thread leak”) of a process that performs multithread processing.
When a thread leak occurs, there is a release leak of resources used by the thread whose termination has been leaked, and other processes or other threads do not use the released leak resources, which reduces the processing speed or operation of the process. Instability may occur.

FIG. 13 is a configuration diagram showing a schematic configuration of a thread leak determination apparatus according to the second modification of the present invention. In the figure, a thread leak determination device (computer resource release leak determination device) 7 includes an operation input unit 11, a display unit 12, a thread number acquisition unit (computer resource usage acquisition unit) 81, and a maximum value update count. Unit 82, thread leak determination unit (release leak determination unit) 83, countermeasure processing execution unit 24, and storage unit 91. The storage unit 91 includes a process information storage unit 311, a thread number information storage unit 912, a determination condition information storage unit 913, a processing content information storage unit 314, and a processing result information storage unit 315.
In the figure, the same reference numerals (11, 12, 24, 311, 314, 315) are given to the portions having the same functions as those in FIG.

The thread number information storage unit 912 replaces the initial value, maximum value, and current value of the memory usage of each process being executed with the initial value, maximum value, and current value of the thread number of each process being executed. It differs from the memory usage information storage unit 312 of FIG. 1 in that it stores a thread number threshold value (determination threshold value for the current value of the thread number) instead of the memory usage threshold value.
The determination condition information storage unit 913 is different from the determination condition information storage unit 313 of FIG. 1 in that it stores a thread count threshold calculation coefficient instead of the memory usage threshold calculation coefficient. The thread number threshold value calculation coefficient is a coefficient for calculating the thread number threshold value similarly stored in the thread number information storage unit 912 by multiplying the thread number initial value stored in the thread number information storage unit 912.

The thread number acquisition unit 81 acquires the thread number of each process being executed from the OS, and stores thread number information including the initial value, current value, and thread number threshold of the number of threads of each process in the thread number information storage unit 912. At the point of writing, the memory usage of each process being executed is acquired from the OS, and the memory usage information including the initial value, current value, and memory usage threshold of the memory usage of each process is stored in the memory usage information storage unit. Different from the memory usage acquisition unit 21 of FIG.
The maximum value update count counting unit 82 determines whether or not the maximum value of the number of threads has been updated. If it is determined that the maximum value has been updated, the maximum number of threads and the maximum value update stored in the thread number information storage unit 912 are determined. In the point of updating the number of times, it is determined whether or not the maximum value of the memory usage has been updated. If it is determined that the maximum value has been updated, the maximum value of the memory usage stored in the memory usage information storage unit 312 This is different from the maximum value update count counter 22 in FIG. 1 that updates the maximum value update count.
The thread leak determination unit 83 reads the current value of the thread number, the maximum value update count, and the thread count threshold value from the thread number information storage unit 912, reads the update count threshold value from the determination condition information storage unit 913, and determines the maximum value update count. The current value of memory usage and the maximum value from the memory usage information storage unit 312 are determined in that it is determined that there is a thread leak when the threshold is greater than or equal to the update count threshold and the current value of the thread count is greater than or equal to the thread count threshold. The value update count and the memory usage threshold are read, the update count threshold is read from the determination condition information storage unit 313, the maximum value update count threshold is equal to or greater than the update count threshold, and the current value of the memory usage is the memory usage 1 is different from the memory leak determination unit 23 of FIG.

Since the thread leak determination device 7 determines the presence or absence of a thread leak based on the maximum number of updates of the number of threads, the thread leak determination device 7 is compared with the thread leak determination device that determines the presence or absence of a thread leak only by whether or not the number of threads is equal to or greater than a threshold The thread leak can be detected at an earlier stage where the number of threads is less than the threshold value.
If no thread leak actually occurs and the number of threads of the thread leak determination target process (hereinafter referred to as “target process”) has only temporarily increased, the thread leak determination apparatus 7 It can be determined that there is no thread leak based on the maximum number of updates of the number of threads of the target process.

Also, even if the thread increase rate is a large value, such as when a process that uses a large number of threads is running for a certain period of time, if the thread leak does not occur, the number of threads is within a certain range. It can be expected that the maximum update count of the number of threads does not exceed the maximum update count threshold. In this case, the thread leak determination device 4 can determine that there is no thread leak. In this respect, the thread leak determination device 7 is less likely to make an erroneous determination as to whether or not there is a thread leak regardless of the increase rate of the number of threads.
Furthermore, when a thread leak occurs, the number of threads may continue to increase regardless of the increase rate of the number of threads. Even when the rate of increase in the number of threads is small, the thread leak detection device 7 increases the number of threads when the maximum number of updates of the number of threads is equal to or greater than the update count threshold and the number of threads is equal to or greater than the thread count threshold. It can be determined that there is a thread leak by detecting that it is continuing. Also in this respect, the thread leak determination device 7 is less likely to make an erroneous determination as to whether or not there is a thread leak regardless of the increase rate of the number of threads.

Further, the thread leak determination unit 83 determines whether or not the current value of the number of threads of the target process is greater than or equal to the threshold for the number of threads in addition to whether or not the maximum number of updates of the number of threads of the target process is equal to or greater than the threshold for the maximum number of updates. Based on this, it is determined whether there is a thread leak. Thereby, when there is no thread leak and the number of open fills of the target process falls within a certain range, it is possible to reduce erroneous determination that there is a thread leak by gradually increasing the number of threads in the normal operation of the process.
Further, the thread leak determination device 7 is erroneously determined even if the thread number threshold is set to a small value, as compared with the thread leak determination device that determines whether or not there is a thread leak only by whether or not the number of threads of the process is equal to or greater than the threshold. The possibility can be reduced. Because even if the number of threads in the target process temporarily or periodically exceeds the thread number threshold, the thread leak is determined by determining whether the maximum number of updates in the target process is greater than or equal to the maximum value update count threshold. This is because it is possible to reduce the possibility of misjudgment that there is a thread leak even though no occurrence has occurred.
Therefore, a thread leak determination device that determines the presence or absence of a thread leak based only on whether or not the number of threads in the process is equal to or greater than a threshold value can detect a thread leak when the number of threads in the target process is small, that is, earlier.

  Further, in the thread leak determination device 7, the thread number acquisition unit 81 sets a value obtained by multiplying the initial value of the thread number by the thread number threshold calculation coefficient, that is, a value obtained by multiplying the initial value of the thread number by a predetermined constant, as the thread number threshold. The thread leak determination unit 83 determines the presence or absence of a thread leak using the thread number threshold. As described above, the thread leak determination unit 83 determines the presence / absence of a thread leak using the thread number threshold set in accordance with the scale of the process to be determined, so it can be expected that the presence / absence of the thread leak can be determined more accurately. .

As described above, the memory leak determination apparatus 1 may be realized in a computer. Similarly, the file leak determination device 4 and the thread leak determination device 7 may be realized in a computer. Specifically, a program for realizing all or part of the functions of the memory leak determination device 1, the file leak determination device 4, and the thread leak determination device 7 is recorded on a computer-readable recording medium. Processing of each unit may be performed by causing a computer system to read and execute a program recorded on a recording medium. Here, the “computer system” includes an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like without departing from the gist of the present invention.

  The present invention is suitable for use in a resource release leak determination device, a memory leak determination device, a resource release leak determination method, and a program.

DESCRIPTION OF SYMBOLS 1 Memory leak determination apparatus 11 Operation input part 12 Display part 21 Memory usage acquisition part 22, 52, 82 Maximum value update frequency count part 23 Memory leak determination part 24 Countermeasure process execution part 31, 61, 91 Storage part 311 Process information storage Unit 312 Memory usage information storage unit 313, 613, 913 Determination condition information storage unit 314 Processing content information storage unit 315 Processing result information storage unit 4 File leak determination device 51 Open file number acquisition unit 53 File leak determination unit 612 Number of open files Information storage unit 7 Thread leak determination device 81 Thread number acquisition unit 83 Thread leak determination unit 912 Thread number information storage unit

Claims (4)

A memory leak determination apparatus for determining whether or not a memory leak occurs when a process uses memory,
A memory usage acquisition unit for acquiring the memory usage of the process;
A maximum value update count counter for counting the maximum update count of the memory usage acquired by the memory usage acquisition unit;
A memory leak determination unit that determines the presence or absence of the memory leak based on the maximum value update number counted by the maximum value update number counting unit;
Equipped with,
The memory leak determination unit updates the maximum value using a value obtained by multiplying a memory usage initial value, which is the memory usage first acquired by the memory usage acquisition unit first after a predetermined time from a process startup, by a predetermined constant, as a threshold value. A memory leak determining apparatus , wherein the memory leak is determined to be present when the number of times exceeds a predetermined number and the memory usage amount is equal to or greater than the threshold value . The memory leak determination device according to claim 1 , wherein the memory usage amount acquisition unit acquires a total value of memory usage amounts of a plurality of the processes as the memory usage amount. A memory leak determination method of a memory leak determination apparatus for determining whether or not a memory leak occurs when a process uses memory ,
Memory usage acquisition unit, and memory usage acquiring the memory usage of the process,
Maximum value update count counting section, and the maximum value update count counting step for counting the maximum number of updates of the memory usage the memory usage acquisition unit acquires,
Memory leakage determination unit, based on the maximum value update number of times the maximum value updating count counting section counts, memory leakage determination step of determining whether said memory leaks,
Equipped with,
In the memory leak determination step, the memory leak determination unit is a value obtained by multiplying a predetermined constant by a memory usage initial value that is the memory usage first acquired by the memory usage acquisition unit after a predetermined time has elapsed since process startup. A memory leak determination method , wherein the memory leak is determined to be present when the maximum value update count is greater than or equal to a predetermined count and the memory usage is greater than or equal to the threshold . In a computer as a memory leak determination device that determines the presence or absence of a memory leak when a process uses memory ,
And memory usage acquiring the memory usage of the process,
A maximum value update count counting step for counting the maximum value update count of the memory usage acquired in the memory usage acquisition step ;
A memory leak determination step for determining the presence or absence of the memory leak based on the maximum value update count counted in the maximum value update count counting step ;
Was executed,
In the memory leak determination step, the maximum value update count is more than a predetermined count, with a value obtained by multiplying a memory usage initial value, which is the memory usage initially acquired after a certain time has elapsed from the start of the process, by a predetermined constant. A program for determining that there is a memory leak when the memory usage is equal to or greater than the threshold value .

Images