JP2006107197A - Memory control method and program and terminal equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide terminal equipment enhancing the use efficiency of a memory by complying with an application program. <P>SOLUTION: A memory securement section 11 receives a securement request for a memory from application. A memory amount management section 13 verifies whether the requested memory has the possibility of memory amount securement and secures the requested amount when possibility is found. A memory release section 12 receives a release request for the memory from the application to release the memory and informs the memory amount management section 13 of the release of the memory. The memory amount management section 13 manages the residual memory amount of a system and the used memory amount of each application. When the residual memory amount of the system is below the securement request for the memory, a memory forced release section 14 selects the appropriate application and releases part or all of the memories used by the application. The memory forced release section 14 requests the objective application to execute forced release for part or all of the memories, thereby executing the forced release. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a memory load control method, a program, and a terminal device, and more particularly to a memory control method and program when a plurality of application software uses a memory, and a terminal device that executes the control method.

  In order to perform memory load control of the system such as conventional paging and swapping, secondary storage is required. However, it is difficult to provide a low-cost and large-capacity secondary storage device such as a hard disk in a terminal device, particularly a mobile terminal device (mobile terminal device), due to restrictions on durability, size, weight, power consumption, and the like. Therefore, it does not have a so-called memory load control function. In a device that does not have a memory load control function, a memory that has been paid out cannot be picked up (stealed by paging or swapping) even for higher priority processing. Therefore, many of the conventional portable terminal devices reserve memory in advance for high-priority processing, or reserve memory to be used for each application (each application), and use memory reserved for each other. A method of guaranteeing the amount of memory by not eroding is taken.

  That is, in the conventional portable terminal device, the following method is adopted in order to guarantee the memory for the operation when the high priority processing occurs. (1) A memory area is divided for each application, and a certain amount of memory is secured by not eroding each other. Not all applications are necessarily divided, but there are also gradual division methods of high priority and others. (2) An upper limit value is set for each application, and securing beyond the upper limit value is guaranteed by limiting the securing beyond this. The method (2) does not divide the area explicitly as in (1), but the memory amount is the same in that it is necessary to prepare the total value of the upper limit values of each application as a system.

  By the way, in an information processing apparatus or the like, an apparatus that performs efficient resource management of a memory is known. For example, in Patent Document 1, one or more programs are selected from the main memory and the programs expanded in the main memory, and the page frame in the main memory allocated to the selected program is released. A resource management device used in an information processing system including a memory release program that enters a sleep state later is described. This apparatus acquires the number of empty page frames in the main memory, and makes the memory release program executable when the acquired number of empty page frames is below a predetermined number of page frames.

  Further, in Patent Document 2, a job group for performing page stealing is determined based on the importance level of a preset job, and a free page is secured based on the determination, so that a main job group with high importance level is secured. A memory management device that avoids memory shortage is described. This apparatus includes a central processing unit, a job group determination unit that registers jobs in a job group formed by grouping jobs according to importance, a memory allocation processing unit that allocates real pages, and a memory that releases memory The memory management unit includes a replenishment processing unit, and the main storage device includes a memory monitoring unit that monitors the use state of the main memory. When the number of free pages in the memory is insufficient, the memory monitoring unit determines a job group to perform page stealing and a job based on the job importance set in advance. Based on this determination, a real page is released from a job belonging to a group of low importance step by step through the memory replenishment unit to secure a free page.

  On the other hand, even in an information terminal device such as a PDA (Personal Data Assistance, Personal Digital Assistants), for example, as disclosed in Patent Document 3, information that solves the shortage of memory capacity when a plurality of application software is started A terminal device is known. This apparatus is an information terminal device that includes a plurality of application software, and starts up the application software designated as the activation target in a predetermined memory. This apparatus includes an execution area determination unit that determines whether or not an execution area of application software specified as an activation target when the application is started can be secured in a memory, and an execution area of application software specified by the execution area determination unit A memory management unit that forcibly terminates the corresponding application software in ascending order of priority and releases it from the memory, and secures the designated application software execution area in the memory .

Japanese Patent Laid-Open No. 2000-215099 (FIG. 2) Japanese Patent Laid-Open No. 2002-244869 (FIGS. 1 and 2) JP 2003-15892 A (FIGS. 1 and 7)

  However, the memory control technology in the conventional portable terminal device has the following problems. The first problem is that the use efficiency of the memory is poor and a larger amount of mounting memory is required. The reason is that a memory division loss occurs when the memory area is divided in advance or an upper limit value is set.

  The second problem is that the application may not operate depending on the situation. The reason is that the memory usage of the application is limited, so that even if the memory is free, operation exceeding the upper limit cannot be performed.

  In order to solve the above problems, if the memory load control method by secondary storage in the information processing device or the like is applied to the system memory of the terminal device, the memory use efficiency becomes extremely poor or the application The program may not work. In other words, secondary storage is difficult to apply to memory management in a small size such as the system memory of a terminal device in order to acquire and release memory in large units such as pages.

  On the other hand, the information terminal device of Patent Document 3 is capable of memory management in a small size, but is limited to memory management at the time of application activation. Furthermore, in mobile terminal devices, etc., there is a difference in the degree of release (whether to release all or part) depending on the type of application program when releasing memory, but it is configured to handle this It is not, and the memory utilization efficiency is bad.

  An object of the present invention is to provide a memory control method, a program, and a terminal device that increase the memory utilization efficiency corresponding to an application program.

  A terminal device according to one aspect of the present invention that achieves the above object is a terminal device that controls a system memory to execute an application program. This terminal device manages the remaining amount of system memory and the amount of memory used by each application program. When the remaining amount of system memory falls below the required amount of memory reservation, one of the system memories used by the selected application program selected. A memory amount management unit that notifies the memory forced release unit so as to release all or all of them. In addition, when a memory allocation request is received from an application program, a request is made to the memory amount management unit to check whether the required memory amount can be secured, and if it can be secured, a memory securing unit that secures the required memory amount and a system from the application program A memory release unit is provided that releases a system memory used in response to a memory release request and notifies the memory amount management unit that the system memory has been released. In addition, a memory forced release unit is provided that forcibly releases the system memory for the selected application program in response to a notification from the memory amount management unit.

  In the terminal device according to the first development mode, the memory amount management unit includes a storage unit that stores a priority associated with each application program, and selects a predetermined application program based on the stored priority. You may do it.

  In the terminal device of the second development form, when the system memory in use of the application program is released when the system memory is overloaded, the system memory that can be operated at least by the application may be left and released.

  In the terminal device according to the third development mode, the memory amount management unit manages the system memory used by the application program in n levels (n is an integer of 2 or more), and the memory securing unit secures the system memory. At this time, one of the n levels may be designated, and the memory releasing unit may designate one of the n levels when releasing the system memory being used by the application program.

  In the terminal device according to the fourth development mode, the memory amount management unit can release the system memory, the first memory necessary for the minimum operation of the application program for each application program, and the first memory that can be released if the process is interrupted. It is also possible to manage by dividing into two memories.

  In the terminal device of the fifth development mode, the memory amount management unit may control to preferentially release the second memory when releasing the system memory in use of the application program.

  A memory control method according to one aspect of the present invention is a method in which a terminal device controls a system memory. This method manages the step of receiving a system memory allocation request from an application program together with the allocation request amount, the remaining system memory amount and the amount of memory used by each application program, and whether or not the remaining system memory amount is less than the allocation request amount. And a step of releasing a part or all of the system memory used by a predetermined application program selected in accordance with the priority when the amount is less than the secured request amount.

  In the memory control method according to the first development mode, the system memory is divided into a first memory necessary for the minimum operation of the application program and a second memory that can be released if the process is interrupted. The second memory may be preferentially released when the system memory that is managed every time and the predetermined application program is being used is released.

  A memory control method according to another aspect of the present invention is a method in which a terminal device controls a system memory. This method includes a step of managing the system memory for each application program by dividing the system memory into a first memory necessary for the minimum operation of the application program and a second memory that can be released if the process is interrupted. Also, a step of receiving a system memory allocation request from the application program together with the requested memory amount, a step of searching for the application program having the lowest priority, and checking whether there is a usage amount of the second memory of the searched application program A step of forcibly releasing the second memory when there is a usage amount of the second memory, a step of adding the usage amount of the second memory forcibly released to the remaining amount of the system memory, and the searched application program The step of clearing the usage amount of the managed second memory and when there is no usage amount of the second memory of the searched application program or when the remaining amount of the system memory has not yet reached the required memory amount, Check if there is A step that, if there is another application program, then searches the low priority application programs, comprising the steps of: returning to the step of checking whether there is a usage of the second memory.

  In the memory control method according to the second development mode, a step of checking whether or not there is another application and searching for the lowest priority application program when there is no other application program, and the searched application A step of checking whether or not the first memory usage of the program is present and if there is a first memory usage, the searched application program is forcibly terminated, and all the memory held by the searched application program is deleted. A step of releasing, a step of adding the usage amount of the first memory released by forced termination to the remaining amount of the system memory, a step of clearing the usage amount of the first memory managed for the searched application program, Application program If there is no usage of the first memory, or if the remaining amount of system memory has not yet reached the requested memory amount, a step of checking whether there is another application program, and if there is another application program, And a step of searching for an application program having a low priority and returning to the step of checking whether or not there is a usage amount of the first memory may be included.

  A program according to an aspect of the present invention includes a process for receiving a system memory securing request from an application program together with a securing request amount to a computer constituting a terminal device having a system memory, a remaining system memory amount, and use of each application program Management of the memory amount, checking whether the remaining amount of system memory is below the required amount of secure memory, and system memory used by the predetermined application program selected according to the priority when it falls below the required secure amount And a process of releasing a part or all of.

  In the program of the first development form, the system memory is divided into a first memory necessary for the minimum operation of the application program and a second memory that can be released if the process is interrupted. The second memory may be preferentially released when the system memory that is managed and in use of the predetermined application program is released.

  A program according to another aspect of the present invention can be released to a computer constituting a terminal device having a system memory by releasing the system memory if the processing is interrupted with the first memory necessary for the application program to operate at a minimum. A process for managing each application program separately from the second memory, a process for receiving a system memory allocation request from the application program together with the requested memory amount, a process for searching for the application program with the lowest priority, and the searched application A process for checking whether the second memory of the program is used, a process for forcibly releasing the second memory if there is a second memory used, and a second forcibly released to the remaining amount of the system memory Processing to add memory usage and the searched application If there is no processing to clear the usage amount of the second memory managed for the application program and the usage amount of the second memory of the searched application program, or the remaining amount of the system memory has not yet reached the required memory amount, A process for checking whether there is another application and a process for searching for the application program with the next lowest priority if there is another application program and checking whether there is a usage amount of the second memory. And return processing.

  In the program of the second development form, it is checked whether or not there is another application, and when there is no other application program, a process for searching again for the application program with the lowest priority, and for the searched application program Processing for checking whether or not there is a usage amount of the first memory, and if there is a usage amount of the first memory, the searched application program is forcibly terminated, and all the memory held by the searched application program is released. Processing, processing for adding the usage amount of the first memory released by forced termination to the remaining amount of the system memory, processing for clearing the usage amount of the first memory managed for the searched application program, and searched application The first memory usage of the program is not If the remaining amount of system memory has not yet reached the required amount of memory, the process of checking whether there is another application program, and if there is another application program, the application program with the next lowest priority is selected. You may make it perform further the process which searches and returns to the process which checks whether there is the usage-amount of 1st memory.

  According to the present invention, even in a terminal device or the like that does not have secondary storage for performing memory load control, it is not necessary to reserve a memory in advance for each application to guarantee a certain amount, and memory division loss is reduced. It does not occur and the memory usage efficiency is improved. The reason is that it has a mechanism that allows a part of the memory of an application with a low priority to be released and used in a scene that requires memory load control.

  The memory load control function in the terminal device according to the embodiment of the present invention includes a memory reservation unit (11 in FIG. 1), a memory release unit (12 in FIG. 1), a memory amount management unit (13 in FIG. 1), and a forced memory release. (14 in FIG. 1). The memory securing unit (11 in FIG. 1) receives a memory securing request from the application, checks whether the requested memory can secure the requested amount by the memory amount managing unit (13 in FIG. 1), and secures it if possible. The memory release unit (12 in FIG. 1) receives the memory release request from the application, releases the memory, and notifies the memory amount management unit (13 in FIG. 1) that the memory has been released. The memory amount management unit (13 in FIG. 1) manages the remaining amount of memory in the system and the amount of memory used by each application, and selects an appropriate application when the remaining amount of memory in the system falls below the memory allocation request. Then, part or all of the memory used by the application is released by the memory forced release unit (14 in FIG. 1). The memory forced release unit (14 in FIG. 1) notifies the target application to forcibly release a part or all of the memory, and executes the forced release.

  Terminal devices that do not have secondary storage for memory load control configured as described above can steal (forced release) the amount of memory that exceeds the threshold of the amount of memory used by the application. In addition, even when the remaining amount of memory in the system is insufficient, it is possible to secure a memory for processing with higher priority.

  Note that the terminal device configured as described above may incorporate a processor and implement a memory load control function by a program operating on the processor.

  Embodiments of the present invention will be described in more detail with reference to the drawings. FIG. 1 is a block diagram illustrating a configuration of a memory load control function of a terminal device according to an embodiment of the present invention. In FIG. 1, a system comprising a system memory (heap) 10 and an application group 20 that uses the system memory (heap) 10 is provided with a memory allocation unit 11, a memory release unit 12, a memory amount management unit 13, and a memory forced release unit 14. Configure the memory load control function. The memory amount management unit 13 has a memory information storage area 15. The memory information storage area 15 stores a remaining system memory 16 and management information 17 for each application. The management information 17 includes information of process ID 31, priority 32, required memory upper limit 33, required memory usage 34, and work memory usage 35.

  In this embodiment, the system memory being used by each application is divided into “essential memory” (first memory) and “work memory” (second memory). Here, “essential memory” corresponds to a memory of a memory amount that has been reserved in advance for each conventional application, and in this embodiment, means a memory that is used without being reserved in advance and is not subject to steal instead. It is. It is assumed that when an application requests a memory from the memory securing unit 11, either “essential memory” or “work memory” is specified. It is assumed that the memory secured as “work memory” must be released any time when the forced memory release unit 14 notifies the forced release. The initial value of the remaining system memory 16 is the amount of system memory (heap) 10. The priority 32 and the essential memory upper limit 33 of each application are determined in advance in consideration of the nature of the application. The application group 20 includes a program 21 for performing a normal application mission and a work memory forced release processing program 22 for releasing the work memory at an arbitrary time.

  Next, the operation of the present embodiment will be described in detail with reference to the drawings. In FIG. 1, each application in the application group 20 secures (gets) the memory with the memory securing unit 11 when using the memory from the program 21, and releases (frees) the memory with the memory releasing unit 12 when unnecessary. When the memory is secured by the memory securing unit 11, a type of “essential memory” necessary for the minimum operation of the application or “work memory” that can be released if processing is interrupted at any time is designated. In addition, when each application receives a notification of forced memory release (SIGNAL / message), the memory release unit 12 releases all “work memory” in use by canceling the processing being executed. A release program 22 is prepared and registered. This SIGNAL or message function may be provided in a general OS (Operating System).

  First, the operation of the memory securing unit 11 is shown in FIG. In FIG. 2, the memory securing unit checks whether the memory amount requested by the memory amount managing unit 13 can be secured in step S11. If it can be secured (Y in step S12), the requested amount of memory is secured in step S13. If it cannot be secured (N in step S12), an error is returned.

  Next, the operation of the memory release unit 12 is shown in FIG. In FIG. 3, the memory release unit 12 first releases the designated memory in step S21, designates the type of memory (separate required memory / work memory) and the memory amount released in step S22, and designates the memory amount management unit 13 Notify

  4 and 5 show operations when the memory amount management unit 13 checks whether the requested memory amount can be secured. In FIG. 4, the memory amount management unit 13 first sets the required memory upper limit value 33 when the required memory is an essential memory (Y in step S31) and when the required memory amount is added to the required memory usage 34 of the application. If it exceeds (N in step S32), an error (unsecured) is returned. Otherwise (N in step S31 or Y in step S32), it is checked in step S33 whether the requested memory is less than or equal to 16 in the remaining system memory. If the requested memory is less than or equal to the remaining system memory 16, the requested memory amount is subtracted from the remaining system memory 16 in step S34. Furthermore, in step S35, the required memory amount is added to the required memory usage amount 34 or the work memory usage amount 35 corresponding to the type of the required memory of the application, and OK is returned.

  On the other hand, if the requested memory is larger than the remaining system memory 16 in step S33, it is checked in step S36 whether the requested memory is work memory. If the request memory is a work memory (Y in step S36), an error (unsecured) is returned. If not (N in Step S36), the process proceeds to Step S37 in FIG. 5 to search for the application with the lowest priority. If there is a work memory usage 35 of the searched application (Y in step S38), the process ID of this application is specified in step S39, and the work memory is forcibly released by the memory forced release unit 14. If the forced release is successful (Y in step S40), the work memory amount forcibly released is added to the remaining amount of the system memory in step S41, and the work memory usage 35 of this application is cleared in step S42. If the remaining amount of system memory is equal to or greater than the required memory amount (Y in step S43), the process proceeds to step S34 in FIG.

  If there is no work memory usage 35 of the searched application (N in step S38), if forced release is not successful in step S40, or if the remaining amount of system memory has not yet reached the requested memory amount in step S43, In step S44, it is checked whether there is any other application information. If there is another application (Y in step S44), the application with the next lowest priority is searched (step S45), and the process returns to step S38. If there are no more applications (N in step S44), an error is returned as a memory shortage.

  The operation when the memory management unit 13 notifies the release of the memory is shown in FIG. When notifying the memory release, the memory amount management unit 13 first adds the released memory amount to the remaining system memory 16 in step S51. In step S52, the released memory amount is added to the required memory usage amount 34 or the work memory usage amount 35 corresponding to the released memory type of the application.

  Next, the operation of the memory forced release unit 14 is shown in FIG. A SIGNAL for forced release of work memory is transmitted to the application corresponding to the process ID specified in step S61. The application that has received this SIGNAL executes the work memory forced release processing program 22 registered by interrupting the processing being executed by the OS. Here, the processing being executed is stopped, all the work memories in use are released by the memory release unit 12, and the result is returned to the SIGNAL transmission source by a message. The memory forced release unit 14 waits for a result response message in step S62. If the result is successful (Y in step S63), OK is returned, and if not successful (N in step S63), an error is returned.

  As described above, a part of the memory of the low priority application is partially released in the situation where the memory load control is necessary, such as when the higher priority application requests the memory in the situation where the remaining memory is low. To make it available. In this way, even for a terminal device that does not have secondary storage for performing memory load control, it is not necessary to reserve a certain amount of memory in advance for each application to guarantee a certain amount, There is no loss (memory that is not used but cannot be used by others), and the memory usage efficiency is improved.

  In addition, for a process that requires real-time processing, a total memory amount necessary for executing the process is registered, and when this process is started, the corresponding memory amount is stored by the memory forced release unit 14. release. As a result, a process that requires real-time performance has a high probability of being able to execute the process without causing an interruption in which the memory is released due to the memory being forcibly released due to insufficient memory.

  Next, a second embodiment of the present invention will be described in detail with reference to the drawings. In the second embodiment, the flowchart of FIG. 5 representing the operation when checking whether the requested memory amount of the memory amount management unit 13 of the first embodiment can be secured is replaced with FIG. 8 and FIG. It is. In FIG. 8, all steps perform the same processing as in FIG. However, if there is no other application information in step S44 (N in step S44), that is, if the required memory cannot be secured even if the work memory of all applications is released, the process returns to step S71 in FIG. Only the progress is different.

  Referring to FIG. 9, an application with the lowest priority is searched in step S71, and if this is the requesting application itself (Y in step S72), an error is returned. If it is not the requesting application itself (N in step S72), the required memory usage 34 of this application is checked in step S73. If there is the required memory usage amount 34 (Y in step S73), the application is forcibly terminated in step S74, and all the memory held by the application is released. The forced termination function may be a function (Kill Signal or the like) provided in a general OS (operating system). If the forced termination is successful (Y in step S75), the required memory usage released by the forced termination is added to the remaining system memory in step S76, and the required memory usage 34 of this application is cleared in step S77. To do. If the remaining amount of system memory exceeds the required memory amount in step S78, the process proceeds to step S34 in FIG.

  If there is no required memory usage 34 in step S73 of FIG. 9, if forced termination is not successful in step S75, or if the remaining amount of system memory has not yet reached the requested memory amount in step S78, another application is added in step S79. Check if there is any. If there is another application (Y in step S79), the application with the next lowest priority is searched (step S80), the process returns to step S72, and the same processing is repeated. If there are no more applications (N in step S79), an error is returned as a memory shortage.

  As described above, in the second embodiment, when the required memory cannot be secured even if the work memory of all applications is released, the predetermined memory requested is forcibly terminated in order from the application with the lowest priority. The amount can be secured.

  Further, in the second embodiment, the memory is divided into n levels (n is a natural number of 3 or more), and the level is specified when the memory is secured, without limiting the division of the essential memory and the work memory to two levels. Even when the memory is forcibly released by the memory forcible release means, the memory level can be specified and released.

It is a block diagram which shows the structure of the memory load control function of the terminal device which concerns on the Example of this invention. It is a flowchart showing operation | movement of the memory securing part based on the Example of this invention. It is a flowchart showing operation | movement of the memory release part which concerns on the Example of this invention. It is a 1st flowchart showing operation | movement of the memory amount management part which concerns on 1st Example of this invention. It is a 2nd flowchart showing operation | movement of the memory amount management part which concerns on 1st Example of this invention. It is a flowchart showing operation | movement in the case of notifying memory release in the memory amount management part which concerns on 1st Example of this invention. It is a flowchart showing operation | movement of the memory forced release part which concerns on the Example of this invention. It is a 1st flowchart showing operation | movement of the memory amount management part which concerns on 2nd Example of this invention. It is a 2nd flowchart showing operation | movement of the memory amount management part which concerns on 2nd Example of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 System memory 11 Memory securing part 12 Memory release part 13 Memory amount management part 14 Memory forced release part 15 Memory information storage area 16 Remaining system memory 17 Management information 20 Application group 31 Process ID
32 Priority 33 Required memory upper limit 34 Required memory usage 35 Work memory usage

Claims (14)

A terminal device that controls system memory and executes application programs,
Manages the remaining amount of system memory and the amount of memory used by each application program. When the remaining amount of system memory falls below the amount of memory reservation required, a part or all of the system memory used by the selected application program selected A memory amount management unit that notifies the memory forced release unit to release,
A memory securing unit that receives a memory securing request from an application program, asks the memory amount management unit to check whether the requested memory amount can be secured, and secures the requested memory amount if it can be secured;
A memory release unit that releases a system memory being used in response to a request to release a system memory from an application program, and notifies the memory amount management unit that the system memory has been released;
In response to the notification from the memory amount management unit, forcibly releasing system memory for the selected application program;
A terminal device comprising:   The memory amount management unit includes a storage unit that stores a priority associated with each application program, and selects the predetermined application program based on the stored priority. The terminal device according to 1.   2. The terminal device according to claim 1, wherein when the system memory in use of the application program is released when the system memory is overloaded, the system memory is released leaving a system memory that can be operated at a minimum.   The memory amount management unit manages the system memory used by the application program by dividing it into n levels (n is an integer of 2 or more), and the memory securing unit is one of the n levels when securing the system memory. 2. The terminal device according to claim 1, wherein the memory releasing unit specifies one of n levels when releasing the system memory in use of the application program.   The memory amount management unit manages the system memory separately for each application program into a first memory necessary for the application program to operate at a minimum and a second memory that can be released if the process is interrupted. The terminal device according to claim 1, wherein:   The terminal device according to claim 5, wherein the memory amount management unit performs control so that the second memory is preferentially released when the system memory in use of the application program is released. A method in which a terminal device controls system memory,
Receiving a system memory allocation request from the application program together with the allocation request amount;
Managing the remaining amount of system memory and the amount of memory used by each application program, and checking whether the remaining amount of system memory is less than the required amount of reservation;
Releasing a part or all of the system memory used by the predetermined application program selected according to the priority when it falls below the secured request amount;
A memory control method comprising:   The system memory is managed for each application program by dividing the system memory into a first memory required for the minimum operation of the application program and a second memory that can be released if the process is interrupted. 8. The memory control method according to claim 7, wherein the second memory is preferentially released when the system memory in use of the program is released. A method in which a terminal device controls system memory,
Managing the system memory for each application program by dividing the system memory into a first memory required for the minimum operation of the application program and a second memory that can be released if the process is interrupted;
Receiving a system memory allocation request from an application program together with the requested memory amount;
Searching for the lowest priority application program;
Checking whether there is a usage amount of the second memory of the searched application program;
Forcibly releasing the second memory when there is a usage amount of the second memory;
Adding the usage amount of the second memory forcedly released to the remaining amount of system memory;
Clearing the usage amount of the second memory managed for the searched application program;
If there is no usage of the second memory of the searched application program, or if the remaining amount of system memory has not yet reached the requested memory, checking whether there is another application;
If there is another application program, searching for the next lowest priority application program and returning to the step of checking whether there is a usage amount of the second memory; and
A memory control method comprising: The memory control method according to claim 9, wherein it is checked whether there is another application, and when there is no other application program,
Re-searching for the lowest priority application program;
Checking whether there is a usage amount of the first memory of the searched application program;
If there is a usage amount of the first memory, forcibly terminating the searched application program and releasing all the memory held by the searched application program;
Adding the usage amount of the first memory released by forced termination to the remaining amount of system memory;
Clearing the usage amount of the first memory managed for the searched application program;
If there is no usage amount of the first memory of the searched application program, or if the remaining amount of system memory has not yet reached the requested memory amount, checking whether there is another application program;
If there is another application program, the next step is to search for the application program with the next lowest priority, and to return to the step of checking whether or not the first memory is used,
A memory control method, further comprising: In a computer constituting a terminal device having a system memory,
Processing to receive a system memory allocation request from an application program together with the allocation request amount;
A process of managing the remaining amount of system memory and the amount of memory used by each application program, and checking whether the remaining amount of system memory is less than the required amount of reservation;
A process of releasing a part or all of the system memory used by the predetermined application program selected according to the priority when it falls below the secured request amount;
A program that executes   The system memory is managed for each application program by dividing the system memory into a first memory required for the minimum operation of the application program and a second memory that can be released if the process is interrupted. 12. The program according to claim 11, wherein the second memory is preferentially released when the system memory in use of the program is released. In a computer constituting a terminal device having a system memory,
A process of managing the system memory for each application program by dividing the system memory into a first memory required for the minimum operation of the application program and a second memory that can be released if the process is interrupted;
Processing to receive a system memory allocation request from an application program together with the requested memory amount;
A process for searching for the lowest priority application program;
Processing for checking whether or not there is a usage amount of the second memory of the searched application program;
A process for forcibly releasing the second memory when there is a usage amount of the second memory;
A process of adding the usage amount of the second memory forcibly released to the remaining amount of system memory;
A process of clearing the usage amount of the second memory managed for the searched application program;
If there is no usage of the second memory of the searched application program, or if the remaining amount of system memory has not yet reached the requested memory amount, a process of checking whether there is another application;
If there is another application program, search for the application program with the next lowest priority, and return to the process of checking whether there is a usage amount of the second memory; and
A program that executes The program according to claim 13, wherein
Check if there are other applications, and if there are no other application programs,
The process of searching for the lowest priority application program again;
A process of checking whether or not there is a usage amount of the first memory of the searched application program;
When there is a usage amount of the first memory, a process of forcibly terminating the searched application program and releasing all the memory held by the searched application program;
A process of adding the usage amount of the first memory released by forced termination to the remaining amount of system memory;
A process of clearing the usage amount of the first memory managed for the searched application program;
A process of checking whether there is another application program when there is no usage amount of the first memory of the searched application program, or when the remaining amount of system memory has not yet reached the requested memory amount;
If there is another application program, search for the application program with the next lowest priority, and return to the process of checking whether or not there is a usage amount of the first memory; and
A program that causes further execution.

Images