KR20080075293A - Apparatus and method for recovery of memory leakage process in portable communication system - Google Patents

Abstract

A device and a method for recovering a memory leakage process in a mobile telecom system is provided to prevent memory leakage from transiting the mobile telecom system to an abnormal system, detect a process causing the memory leakage, and restart the process depending on weight of the operated processes. A memory information collector(201) checks and provides memory usage information of a process to a memory leakage determiner(205) at predetermined time intervals. The memory leakage determiner extracts the process causing the memory leakage by using the received memory usage information and provides a list of the memory leakage processes to a memory leakage controller(207). The memory leakage controller restarts the memory leakage process by checking the received memory leakage process list. A memory information database(203) stores required memory information, which represents a memory size used in normal operation of the process, of each process. The memory leakage determiner determines the memory leakage process when the memory usage information of the processor is bigger than the required memory information of the process.

Description

Apparatus and method for recovering a memory leak process in a mobile communication system {APPARATUS AND METHOD FOR RECOVERY OF MEMORY LEAKAGE PROCESS IN PORTABLE COMMUNICATION SYSTEM}

1 is a view showing a process of a memory leak management system for processing a memory leak in a general mobile communication system,

2 is a block diagram illustrating a memory leak management unit for checking a memory leak in a mobile communication system according to an exemplary embodiment of the present invention;

3 is a flowchart illustrating a process for processing a process in which a memory leak occurs in the memory leak management unit according to an exemplary embodiment of the present invention;

4 is a flowchart illustrating a process of a memory information collecting unit collecting memory information in a memory leak managing unit according to an exemplary embodiment of the present invention;

FIG. 5 is a diagram illustrating the form of a message including information of a process in which a memory leak may occur according to an exemplary embodiment of the present invention.

6 is a flowchart illustrating a process of a memory leak determining unit for determining whether a memory leak is performed by a memory leak managing unit according to an exemplary embodiment of the present disclosure;

7 is a diagram showing the configuration of information stored in a memory information database;

8 is a flowchart illustrating a process of a memory leak controller which processes a process restart when a memory leak occurs in the memory leak manager according to an exemplary embodiment of the present invention.

The present invention relates to an apparatus and a method for preventing a memory leak of a process in a mobile communication system, and more particularly, to an apparatus and a method for detecting a process in which a memory leak occurs in order to prevent abnormal operation of the mobile communication system.

1 is a diagram illustrating a process of a memory leak management system for processing a memory leak in a general mobile communication system.

Referring to FIG. 1, the memory leak management system may include a memory information collector 101 and a memory leak controller 103.

The memory information collecting unit 101 acquires the memory usage of the running process (for example, process 1 memory 100MB, process 2 memory 500MB, process 3 memory 400MB, process 4 memory 200MB, etc.) 105).

Thereafter, the memory information collecting unit 101 provides the memory leak control unit 103 with information on a process using the maximum memory among the obtained memory usage of the process (for example, process memory usage 500MB) 107 do.

When the memory leak controller 103 determines that the available memory that can be allocated to the process is insufficient, restarting of the process using information of the process using the maximum memory received from the memory information collecting unit 101 is performed. ).

That is, the memory leak management system as described above may stop the function of performing a normal service by terminating the operation of a process that uses the maximum memory or an application that wants to use a new memory when there is not enough memory available. There is this.

SUMMARY OF THE INVENTION An object of the present invention is to provide an apparatus and method for preventing a transition to an abnormal system according to a memory leak in a mobile communication system.

Another object of the present invention is to provide an apparatus and method for detecting a process in which a memory leak occurs in a mobile communication system.

Another object of the present invention is to provide an apparatus and method for processing restart of a process according to a weight of a process running in a mobile communication system.

According to a first aspect of the present invention for achieving the above objects, a system for recovering a memory leak process of a mobile communication system checks the memory usage information of the process at a predetermined time interval and provides it to the memory leak determination unit. Extracting a process in which a memory leak occurs by using a memory information collecting unit and memory usage information of the process provided from the memory information collecting unit, and providing information about processes in which the memory leak has occurred to a memory leak controller; And a memory leak controller which checks a list of processes in which the memory leak has been provided from the memory leak determiner and restarts the process in which the memory leak has occurred.

According to a second aspect of the present invention for achieving the above object, a method for recovering a memory leak process of a mobile communication system comprises the steps of acquiring memory information for a running process and using the obtained memory information And confirming whether or not the memory leaking process exists, and if the memory leaking process exists, processing to recover the memory leaking process.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted when it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

In the following description, an apparatus and method for preventing a transition to an abnormal system according to a memory leak in a mobile communication system will be described.

In addition, the request memory information for each process defined in the following description refers to information indicating the amount of memory used when the process operates normally, and the mobile communication system in which the memory leak occurs includes a base station and a server providing a service. I mean.

2 is a block diagram illustrating a memory leak management unit for checking a memory leak in a mobile communication system according to an exemplary embodiment of the present invention.

Referring to FIG. 2, the memory leak managing unit 200 includes a memory information collecting unit 201, a memory information database 203, a memory leak determining unit 205, and a memory leak controlling unit 207. can do.

The memory information database 203 includes request memory information for each process operating in the mobile communication system and information of a cycle for confirming the memory usage information for each process.

The memory information collecting unit 201 obtains memory usage information of the process at a cycle stored in the memory information database 203 and provides the memory leak information to the memory leak determining unit 205.

The memory leak determining unit 205 compares the memory usage information of the process received from the memory information collecting unit 201 with the required memory information for each process previously stored in the memory information database 203. Identifies a process that is suspected of having a process memory leak.

Thereafter, the memory leak determining unit 205 registers the process suspected of memory leak in the memory leak suspect list. Here, the memory leak suspect list is a list of items of processes for which memory leak is suspected.

That is, the memory leak determining unit 205 compares the memory usage information of the running process received from the memory information collecting unit 201 with the required memory information for each process previously stored in the memory information database 203. do.

As a result of the comparison, when the memory usage information of the process received from the memory information collecting unit 201 is larger than the requested memory information for each process, the memory leak determining unit 205 may determine that the memory leak of the process is suspected. Can be.

In addition, the memory leak determining unit 205 determines that a memory leak has occurred for processes registered a predetermined number of times in the memory leak suspect list, generates a list of processes in which the memory leak has occurred, and generates the memory leak control unit. Provided at 207.

The memory leak controller 207 checks the list of processes in which the memory leak has been provided from the memory leak determiner 205 and processes the memory leak controller to restart the process in which the memory leak has occurred.

The memory information database 203, the memory information collecting unit 201, the memory leak determining unit 205, and the memory leak control unit 207 may be performed by the memory leak management unit 200. In the present invention, it is separately configured to illustrate each function separately. Therefore, when the actual product is implemented, all of them may be configured to be processed by the memory leak management unit 200.

In the above description, a device for preventing a transition to an abnormal system according to a memory leak in a mobile communication system has been described. In the following description, a memory leak occurring in a mobile communication system using a device according to an embodiment of the present invention is processed. A method for doing so will be described.

3 is a flowchart illustrating a process for processing a process in which a memory leak occurs in the memory leak management unit according to an exemplary embodiment of the present invention.

Referring to FIG. 3, first, the memory leak management unit 200 checks the system operation in step 301, and then proceeds to step 303, in which the memory leak management unit 200 proceeds to step 303. The amount of memory).

Here, the process of checking the memory information used in the process may be performed by the memory information collecting unit 201 under the control of the memory leak management unit 200, the memory information collecting unit 201 Periodically, the kernel receives memory information about all processes running on the system.

In operation 305, the memory leak manager 200 instructs the memory leak determiner 205 to check whether a process suspected of memory leak exists.

Herein, an operation process of the memory leak determining unit 205 received from the memory leak managing unit 200 will be described in detail with reference to FIG. 6.

If the memory leak determining unit 205 receives the information indicating that there is a process in which the memory leak is suspected, the memory leak managing unit 200 proceeds to step 307 and causes the memory leak control unit 207 to proceed. After processing to restart the process where the memory leak occurred, the algorithm is terminated.

3 is a description of the overall operation of the memory leak management unit 200, and in the following description, detailed functions of the leak management unit 200 will be described.

4 is a flowchart illustrating a process of a memory information collecting unit collecting memory information of processes operating in the memory leak managing unit according to an exemplary embodiment of the present invention. In the following description, FIG. 5 illustrates a form of a message including information of a process in which a memory leak may occur.

Referring to FIG. 4, the memory information collecting unit 201 first receives memory information of all processes from the kernel in step 401, and then proceeds to step 403 in which a large amount of memory is used using the received memory information. Create a list sorted in order of process.

In operation 405, the memory information collecting unit 201 acquires information on a process in which a memory leak may occur. In this case, the information on the process that may be determined as the memory leak refers to information on a predetermined number of processes with the highest memory usage among the processes with the most memory usage arranged in step 403.

In operation 407, the memory information collecting unit 201 transmits a message including the obtained process information to the memory leak determining unit 205.

Here, the message transmitted to the memory leak determining unit 205 includes a message head (msg head) 501 indicating that the message including the process information and the information about the process as shown in FIG. It may be configured as a message body (msg body) 503.

Here, the message body msg body 503 may include a message type 505 indicating system processor information, a process ID 507, and a size 509 indicating a process used memory size. ), And a process name (Process) 511.

When the message of the above type is provided to the memory leak determining unit 205, the memory information collecting unit 201 ends the present algorithm.

6 is a flowchart illustrating a process of a memory leak determining unit for determining whether a memory leak is performed in the memory leak managing unit according to an exemplary embodiment of the present invention. In the following description, FIG. 7 is a diagram illustrating a configuration of information stored in the memory information database 203.

Referring to FIG. 6, the memory leak determining unit 205 first receives information on a process that may be determined to be a memory leak from the memory information collecting unit 201 in step 601, and then proceeds to step 603 to leak the memory. Check for suspect processes.

Here, whether there is a process suspected of leaking memory is determined by process information previously received from the memory information collecting unit 201 and stored in the memory information database 203 of the memory leak managing unit 200. The requested memory information can be compared and judged.

FIG. 7A is a diagram showing required memory information previously stored in the memory information database 203.

Referring to FIG. 7A, the request memory information is information indicating the amount of memory used when the process operates normally. The process name (capsName (key)) 701 and the process execution name (exeName) are shown. 703, a memory amount (norm_size) 705 used in the process loading, a maximum memory usage max_size 707 of the process, and a process service importance (isCritical) 709.

FIG. 7B is a diagram illustrating a structure of a threshold value used as a reference for determining whether a memory leak is stored in the memory information database 203.

Referring to FIG. 7B, the threshold 711 includes information indicating the number of times the memory usage has increased (increaseCount) 713, the memory usage increase size (715), and whether the memory leak process is restarted (autoRestart). (717).

That is, when the memory leak determining unit 205 receives the information of the process using more memory than the maximum memory usage max_size 707 of the requested memory information from the memory information collecting unit 201, When the size exceeding the memory usage is larger than the memory usage increase size 715 of the threshold, it may be determined that a memory leak has occurred in the process.

If it is determined in step 603 that the process suspected of memory leak exists, the memory leak determination unit 205 proceeds to step 605 to determine whether the process suspected of memory leak is already registered in the memory leak suspect list. Check it.

If it is confirmed that the process is not registered in the memory leak suspect list, the memory leak determination unit 205 proceeds to step 613 to register the process in the list.

On the other hand, if it is confirmed that the process is already registered in the memory leak suspect list, the memory leak determiner 205 proceeds to step 607 and increases the number of registrations of the memory leak suspect list by "1".

In operation 609, the memory leak determining unit 205 determines whether a process registered in the memory leak suspicion list having a predetermined threshold value or more exists.

If there is no process registered in the memory leak suspicion list greater than or equal to the threshold value, the memory leak determination unit 205 performs the process of step 601 again.

On the other hand, when it is determined that there is a process registered in the memory leak suspicion list having a threshold value or more, the memory leak determination unit 205 proceeds to step 611 to register the process in the memory leak list, and then stores the registered list in memory. It is provided to the leak control part 207.

Here, the list provided to the memory leak control unit 207 is a message head (msg head) 731 indicating that the memory leak is a list of the process as shown in Figure 7 (c) and information about the process It may be configured as a message body (msg body) 733 including a.

Here, the message body msg body 731 may include a message type 735 indicating system processor information, a suspect list registration number 737 of the process, and a process ID in which a memory leak occurs ( 739), the size (741) indicating the process used memory size, and the process name (Process) (743) can be configured.

The memory leak determining unit 205 completes the transfer of the list to the memory leak control unit 207, and then ends the present algorithm.

8 is a flowchart illustrating a process of a memory leak controller which processes a process restart when a memory leak occurs in the memory leak manager according to an exemplary embodiment of the present invention.

Referring to FIG. 8, the memory leak controller 207 receives a memory leak list from the memory leak determiner 205 in step 801.

In operation 803, the memory leak controller 207 calculates the weighted memory of the process identified as the memory leak.

Here, the weighted memory is a value used as a criterion for selection of a process for restarting when the memory of the running process is excessive. The memory leak controller 207 calculates the weighted memory when the memory of the processes is excessively used. Process to restart the process with the size of the weighted memory in the middle.

The memory leak controller 207 proceeds to step 805 to arrange the calculated weight memory sizes in the order of the largest weight memory size, and then proceeds to step 807 to determine whether the available memory of the system is insufficient. If it is confirmed that the available memory of the system is not insufficient, the memory leak controller 207 repeats the process of step 801.

On the other hand, when it is determined that the available memory of the system is insufficient, the memory leak controller 207 proceeds to step 809 to process the process of restarting the large weighted memory, and then ends the present algorithm.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

As described above, by using the apparatus and method for preventing the memory leak according to the present invention, when there is not enough memory available in the existing mobile communication system, the operation of the process that uses the maximum memory or the application to use the new memory By ending the problem, the problem of stopping the function of performing a normal service can be solved.

Claims (8)

In the system for recovering the memory leak process of the mobile communication system, A memory information collection unit which checks the memory usage information of the process at a preset time interval and provides the memory leak determination unit to the memory leak determination unit; A memory leak determining unit configured to extract a process in which a memory leak occurs by using memory usage information of the process provided from the memory information collecting unit, and provide information about processes in which the memory leak occurs to a memory leak controller; And a memory leak controller configured to check a list of processes in which the memory leak has been provided from the memory leak determiner and to restart the process in which the memory leak has occurred. The method of claim 1, The system for recovering the memory leak process of the mobile communication system, And a memory information database for storing request memory information for each process, which is information indicating an amount of memory used when the process operates normally. The method of claim 2, The memory leak determination unit, The memory usage information of the running process received from the memory information collecting unit is compared with the required memory information for each process previously stored in the memory information database. As a result of the comparison, the memory usage information of the process is requested memory for each process. If greater than the information, it can be determined that a memory leak of the process is suspected. The method of claim 3, wherein The memory leak determination unit, And if it is determined that a memory leak is suspected above a predetermined threshold value, the system may determine that a memory leak has occurred in the process in which the memory leak is suspected. In the method for recovering the memory leak process of the mobile communication system, Obtaining memory information about a running process; Checking whether there is a process in which a memory leak occurs using the obtained memory information; If it is determined that the process in which the memory leak has occurred exists, the process of recovering the process in which the memory leak has occurred is included. The method of claim 5, Acquiring the memory information on the running process, Receiving memory information about all running processes; Generating a list in which the memory information of the provided process is sorted in order of high memory usage; And extracting a process using a large amount of memory from the generated list. The method of claim 6, The process of checking whether there is a process in which a memory leak occurs using the obtained memory information may include: Comparing the information of the process with a large amount of memory usage with the required memory information for each process previously stored; Determining that the memory leak of the process is suspected when the memory usage information of the process is greater than the requested memory information for each process; If it is determined that the memory leak is suspected more than a predetermined threshold value, further comprising the step of determining that the memory leak occurred in the process suspected of the memory leak. The method of claim 5, When it is confirmed that the process in which the memory leak has occurred exists, the process of recovering the process in which the memory leak has occurred is performed. Measuring the weighted memory for the process that caused the memory leak, Re-starting the process having the greater weighted memory when determining that there is insufficient memory available.

Images