JPH08314791A - Memory assignment processing method for application - Google Patents

Abstract

PURPOSE: To provide a means which efficiently and quickly performs allocation processing of a memory area like a buffer used for window processing or input/ output processing of an application. CONSTITUTION: An application 11 corresponding to a multi-window system acquires and holds a memory 13 including a memory area 17a corresponding to one window from a system 12 at the time of the start of the application and allocates the held unused memory area at the time of an open request of the first window and additionally acquires and allocates a required memory area from the system 12 at the time of an open request of the second or following window and returns the memory area allocated to the window to be closed to the system 12 to release it at the time of a close request or the window other than the last window and holds the memory area allocated to the window to be closed as an unused memory area at the time of a close request of the last window.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an allocation processing method for a plurality of memory areas such as a window display buffer and an input / output buffer in an application, and in particular, acquisition and release of the memory area according to a request from a program. It is possible to quickly and efficiently allocate a memory area to a request when the above is repeated.

[0002]

2. Description of the Related Art Conventionally, when an application capable of displaying a plurality of windows with multi-window support is being operated by an OS such as Windows capable of operating a plurality of applications, the memory area acquired by the window being displayed is displayed as a window. If another application acquires that memory area after releasing it for closing, etc., and there is no other free memory area, the memory will be insufficient even if you return to the original application and open the window again. There was a case that could not be executed.
FIG. 10 illustrates this.

In FIG. 10, an application (abbreviation of application, the same applies hereinafter) 1 has a window 1 open, and the window 1 has acquired a memory 1 for use. Indicates that application 1 then closes window 1 and releases memory 1 for window 1. Shows a state in which the application 2 is activated next time and the memory 1 for the released window 1 is acquired.
After that, the application 1 opens the window 1 to issue a memory acquisition request, but the memory is insufficient and the window 1 cannot be opened. For this reason, it is necessary to open the window 1 again with the application 1 after the processing of the application 2 is finished, which causes a problem that the application processing is stagnant.

Further, the application requests the system to acquire the memory required for opening the window or during processing in the window, and receives the memory allocation from the system, but the size of the memory required by the window is It has a width of several bytes to several tens of kilobytes, and requesting each system to acquire a small-sized memory such as several bytes or hundreds of bytes will take time and increase the system load, resulting in poor efficiency. There is a problem that the processing speed is reduced. One way to improve this problem is to acquire a large amount of memory from the system that each window may use in advance, and manage each window to use that memory as needed. . However, with this method, the memory management load on each window increases, processing may become complicated, and abnormal operation may occur, and memory may be wasted and use efficiency may decrease.

Similar problems also occur when acquiring buffers used in input / output processing and communication processing of applications.

[0006]

SUMMARY OF THE INVENTION It is an object of the present invention to provide means for efficiently and quickly allocating a memory area such as a buffer used in window processing and input / output processing of an application. .

[0007]

According to the memory allocation processing method of the present invention, the number of memory acquisition requests made by an application to the system is reduced, and quick memory allocation can be performed in response to a memory acquisition request from an application. Therefore, (1) When the application is started, the memory including the memory area for one buffer is acquired from the system and held, and when a buffer acquisition request is made and the buffer is the first one, When an unused memory area held by the application is allocated, and when the buffer is the second or later one, the necessary memory area is additionally acquired from the system and allocated, and when there is a buffer release request, If that buffer is not the last one, the system allocates the memory area allocated to that buffer. Return to releasing the application held by the unused memory area allocated to the buffer when the other the buffer was the last first sheet,
It is characterized by the following. (2) In (1), each process of allocating a memory area when requesting to acquire a buffer and releasing and holding the memory area when requesting to release a buffer is executed by the memory management routine provided in the application. Characterize. (3) A memory area for a plurality of predetermined blocks is acquired from the system when the application is started. The acquired memory area manages the used state and the unused state in block units, and when a buffer acquisition request is made, Allocate the required number of unused blocks in the memory area obtained from the above system, and if there are no unused blocks, allocate additional blocks of the required memory area from the system and allocate the buffers. When the block request of the buffer is acquired from the system when the application is started, the buffer block is not returned to the system and is retained as an unused block in the application. If the block of the created buffer is an additional one acquired from the system, The feature is that it is returned to the stem and released. (4) In (3), the processing corresponding to the buffer acquisition request and the buffer release request is executed by the memory management routine provided in the application, and the usage status of the memory area block acquired from the system when the application is started and the status The use state is managed by using a flag.

[0008]

According to the present invention, in the case of a multi-window compatible application, the minimum required memory for operating the application is acquired at the time of starting the application, and the minimum required memory is not released even when the window is closed. To do so.

However, since it is compatible with multiple windows,
If you open two or more windows and do not release the memory when you close the windows, the memory will be taken enough to repeat the open / close. Therefore, if you open / close two or more windows, acquire the memory. After releasing the application, at least one window can be opened even if another application is activated.

Further, when the first window is opened, the memory already acquired at the time of starting is used, and when the second window is opened, a new memory is acquired, and then the first window is acquired.
When the window is closed, the memory used in the first window is released. After that, when the second window is closed, the memory is not released and the window opened next is used.

After all, when a plurality of windows are open, only the memory used by the last window is left unreleased so that the window opened next can be used.

Further, according to the present invention, the processing speed is deteriorated when the system is requested to have a memory of several bytes every time it is needed. Therefore, a method of previously acquiring the memory to be used is used. The process of pseudo acquisition and release of memory is added to each window instead of performing the process to simplify the process of each window and increase the processing speed.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a processing outline diagram of an embodiment of the present invention corresponding to claims 1, 2, 5, and 6, 11 is an application compatible with multi-window, and 12 is a system having a multi-window control function ( OS), 13 is the main memory (M
S), 14 is a display screen, 15 is a processing routine for performing multi-window screen output in the application 11 under the support of the system 12, 16 is a memory management routine for allocating memory areas to windows, and 16a is a memory area. Allocation management table, 17
Is a memory area acquired by the application 11 at startup, 17a is a window memory area included in the memory area 17, and 17b is a window memory area additionally acquired from the system for another window.

FIG. 2 is a processing flow of the embodiment shown in FIG. The operation will be described below with reference to FIGS. 1 and 2.
First, the flow when the window shown in FIG. 2A is opened will be described. The application 11 acquires the memory area 17 from the system 12 as one of the operating environments required at the time of activation. The memory area 17 includes a memory area 17a sufficient to open one window.

The processing routine 15 of the application 11
When a window open request is generated during the operation of, a request for acquisition of the memory area required for opening is issued. In response to this, the memory management routine 16 performs memory allocation processing.

The window requested to be opened here is 1
If it is the first one, the memory area 17a reserved for the window is allocated in the memory area 17 already acquired when the application is started. Thereby, for example, the window 1 is opened on the display screen 14.
On the other hand, when the window requested to be opened is the second or later window, a memory acquisition request is issued to the system 12, and the memory area 17b is additionally acquired and allocated to the window. Thereby, for example, the window 2 is opened on the display screen 14.

Next, the flow when the window shown in FIG. 2B is closed will be described. When the processing routine 15 issues a window close request by the processing, the memory management routine 16 releases (returns to the system) the memory area corresponding to the memory area unless the window is the last one displayed on the screen. Perform processing. However, if the window to be closed is the last one remaining on the screen, the memory area corresponding to it is not released, and the memory management routine 16 is left as it is.
Managed and owned. The memory management routine 16 has a memory area allocation management table 16a for these memory allocation processes, and manages each acquired memory area in association with an allocation destination window or an unused state. The released memory area is deleted from the table. 3 to 5 show specific examples of the memory allocation process.

FIG. 3 shows an example of a memory allocation process when one window is opened. Then, app 1
The memory (memory area) for window 1 is acquired when is started. Then, window 1 is opened. At this time, the acquired memory for window 1 is used.
Then window 1 is closed, but window 1
The memory for is not released because window 1 was the last one on the screen. Therefore, even if another application 2 (not shown) is activated thereafter, the application 2 will not acquire this memory. The memory for the window 1 is released when the application 1 ends.

4 and 5 show an example of the memory allocation process when a plurality of windows are opened. FIG.
In this case, the first window 1 is opened, and the memory for the window 1 acquired at the start of the application 1 at this time is used. In FIG. 4, the application 1 opens the second window 2. At this time, the memory for window 2 is acquired from the system and used.

In FIG. 5, the window 1 is closed following that of FIG. As a result, the memory for window 1 is released (returned to the system). In FIG. 5, the window 2 is further closed. For this reason, the memory for window 2 is unnecessary, but it is not released because window 2 is the last one on the screen,
Owned by App 1. In FIG. 5, the application 1 opens the window 1 again. In this case, the window 2 that was previously used by the window 2 owned by the application 1
Memory for window 1 is allocated. Even if another window is opened instead of the window 1, the memory for the window 2 is used for that window. These processes can be repeated any number of times.

FIG. 6 is a process outline diagram of an embodiment corresponding to claims 3, 4, 7, and 8. Note that the same reference numerals are used for the elements common to FIG. In FIG. 6, when the application 11 is started, a memory area 17c including blocks for a plurality of windows is acquired in advance, and the used / unused state of each block is managed by a flag 16b.

FIG. 7 shows a processing flow of the memory management routine 16 in the embodiment of FIG. The operation of the embodiment of FIG. 6 will be described below according to the flow of FIG. FIG. 7A is a flow at the time of memory acquisition. When a memory acquisition request is issued from the multi-window processing routine 15 of the application 11, a memory acquisition request is made by referring to the flag 16b. A block in the area 17c is found and assigned. If there is no unused block, an additional memory area is acquired from the system 12 and allocated. The additional / acquired memory area is not managed by the flag 16b for the used / unused state.

FIG. 7B is a flow of the memory release process. When a memory release request is issued from the processing routine 15 with the window close, it is checked whether the designated memory area is managed by the flag 16b. However, if managed by the flag 16b, the corresponding flag is set to an unused state and is not returned to the system 12. However, if the designated memory area is not managed by the flag 16b, it is returned to the system 12 and released.

FIG. 8 shows a concrete example of the processing of the memory management routine 16 in the embodiment of FIG. FIG. 8A shows a process when a memory is acquired. When the window requests the memory management routine to acquire the memory, the memory management routine searches for the used / unused flag of the memory, and the unused memory area is searched. Find (block). When an unused memory area is found, the window is notified of the area. When there is no unused memory area, the area is acquired from the system, and the memory area acquired from the system is notified to the window.

FIG. 8B shows the processing at the time of memory release. When there is a memory release request from the window, the memory management routine determines whether the memory area (block) requested by is the memory area acquired at the time of startup. Is checked by the flag. If it indicates that the requested memory area is the memory area that was acquired at startup, change the flag (displaying the usage status) to the unused status and the requested memory area is started. If it is not the acquired memory area, the memory area is returned to the system and released.

FIG. 9 shows a memory management function tree of the memory management routine. Broadly speaking, (1) memory acquisition function at application startup, (2) memory acquisition function by request from window, (3) memory release function by request from window, and (4) memory release function at application termination And (2) is (2-
1) A function to additionally acquire and allocate from the system, and (2
-2) Divided into the function of allocating the memory acquired at startup, (3) is (3-1) the function of returning the additionally acquired memory to the system and releasing it, and (3-2) As the acquired memory as it is. It is divided into functions that it possesses.

Although the embodiment described above is concerned with the multi-window processing, the present invention is also applied to the case where the number of buffers or the buffer size is increased or decreased according to the processing request such as the I / O buffer or the communication buffer. What you can do is self-evident.

[0028]

According to the present invention, the following effects can be obtained. -It is possible to prevent the OS from becoming inoperable due to lack of memory after booting in an OS (such as Windows) that can run multiple programs.

(Especially for applications running on Windows, this is effective because windows are mainly used.) ・ When not only the memory used for windows but also a plurality of the same type of memory, the same logic causes a memory shortage. You can prevent and reuse memory.

When operating this application (after starting), the system will not stop due to lack of memory. -Excellent portability because the structure does not depend on the OS.

The processing of each window is simplified by only performing normal memory acquisition / release processing, and eliminating the need for troublesome memory management. -Processing performance is faster because memory is not always acquired from the system for a small memory area.

When not only one type of memory but a plurality of memories of the same type are used, it is possible to simplify the acquisition / release of memory with the same logic.

[Brief description of drawings]

FIG. 1 is a process schematic diagram of a first embodiment of the present invention.

FIG. 2 is a processing flow of the first embodiment.

FIG. 3 is an explanatory diagram (part 1) of a specific example of the memory allocation processing according to the first embodiment.

FIG. 4 is an explanatory diagram (part 2) of the specific example of the memory allocation process according to the first embodiment.

FIG. 5 is an explanatory diagram (part 3) of the specific example of the memory allocation processing according to the first embodiment.

FIG. 6 is a process schematic diagram of the second embodiment of the present invention.

FIG. 7 is a processing flow of a memory management routine in the second embodiment.

FIG. 8 is an explanatory diagram showing a specific example of processing of a memory management routine in the second embodiment.

FIG. 9 is a memory management function tree diagram of a memory management routine.

FIG. 10 is an explanatory diagram of a memory allocation process of a conventional application.

[Explanation of symbols]

 11: Application 12: System (OS) 13: Main memory (MS) 14: Display screen 15: Processing routine 16: Memory management routine 16a: Memory area allocation management table 16b: Flags 17, 17a, 17b, 17c: Memory area

Claims (8)

[Claims] 1. In a memory allocation processing method for an application, a memory including a memory area for one buffer is acquired from the system at the time of starting the application, and is retained, and when a buffer acquisition request is made, the first buffer is acquired. If it is, the unused memory area held by the application is allocated, while the buffer has 2
If it is the first or subsequent one, the necessary memory area is additionally acquired from the system and allocated. When a buffer release request is made, if that buffer is not the last one, it is allocated to that buffer. The memory area used to be returned to the system is released, and on the other hand, if the buffer is the last one, the application holds the memory area allocated to the buffer as unused. Allocation processing method in the application to be used. 2. The memory management routine according to claim 1, wherein each process of allocating a memory area when a buffer acquisition request is made and releasing and holding a memory area when a buffer release request is made is executed by a memory management routine provided in an application. A memory allocation processing method in an application characterized by the above. 3. A memory allocation processing method for an application, wherein a memory area for a plurality of predetermined blocks is acquired from the system when the application is started, and the acquired memory area manages a used state and an unused state in block units. , When a buffer acquisition request is made, the required number of unused blocks in the memory area obtained from the system above are allocated. If there are no unused blocks or there are insufficient blocks, the memory area required by the system. Block is additionally acquired and allocated, and when there is a buffer release request, if the block of the buffer was acquired from the system when the above application was started, it is not returned to the system and is unused by the application. As a block of the A method for allocating memory in an application, wherein if the block of the buffer is additionally acquired from the system, it is returned to the system and released. 4. The use state of a block of a memory area acquired from the system at the time of starting an application, wherein a process corresponding to a buffer acquisition request and a buffer release request is executed by a memory management routine provided in the application. A method for processing memory allocation in an application, characterized in that management of unused states is performed using flags. 5. A memory allocation processing method for a multi-window application, wherein a memory including a memory area for one window is acquired from the system and held when the application is started, and when a window open request is issued, the window is opened. If the window is the first one, the unused memory area held by the application is allocated, while if the window is the second or later one, the necessary memory area is additionally acquired from the system. When a window close request is made and the window is not the last one, the memory area allocated to that window is returned to the system and released, while that window is the last one. If it is an eye, the memory area allocated to the window A memory allocation processing method in an application, characterized in that the application holds the area as unused. 6. The memory management routine according to claim 5, wherein each process of allocating a memory area when a window open request is issued by an application and releasing and holding the memory area when a window close request is issued are performed by a memory management routine provided in the application. A memory allocation processing method in an application characterized by executing. 7. A method for allocating memory in a multi-window compatible application, wherein a memory area for a plurality of predetermined blocks is acquired from the system when the application is activated, and the acquired memory area is used and unused in block units. When the window requests the acquisition of the memory area, the required number of blocks in the unused area of the memory area obtained from the above system is allocated. If there are no unused blocks or there are insufficient blocks, When a block of the memory area is acquired from the system when the window is requested to release the block of the memory area and the block of the memory area is additionally acquired and allocated from the system, Application without returning it to the system Application, which holds it as an unused block on the other hand, and returns it to the system and releases it if the block of the memory area requested to be released is additionally acquired from the system. Memory allocation processing method in. 8. The process according to claim 7, wherein the process corresponding to the acquisition request and the release request of the memory area from the window is
A memory allocation processing method for an application, which is executed by a memory management routine provided in the application, and flags are used to manage the use status and unused status of blocks of the memory area acquired from the system when the application is started. .