KR20220017309A - Method for allocating of virtual memory and electronic device supporting the same - Google Patents

Abstract

Disclosed is an electronic device, which includes: a memory for storing an application; and a processor operatively connected to the memory, wherein the processor is configured to: set information indicating a failure of the memory allocation, if memory allocation for virtual memory corresponding to the application fails during the execution of the application, determine the size of a heap area comprised in the virtual memory on the basis of the set information, if the set information exists when the application is re-executed, and allocate the virtual memory comprising the heap area of the determined size. Other various embodiments identified through the present document are possible. Accordingly, it is possible to maximize efficiency of a storage space of the virtual memory.

Description

Method for allocating of virtual memory and electronic device supporting the same

Various embodiments of the present invention relate to virtual memory allocation techniques.

An electronic device (or computing device) that processes or performs data processing may include a memory for storing data or instructions used by an executed application. In order to more efficiently use the limited storage space of the memory, the electronic device may use the virtual memory to provide more storage space than the actual memory capacity. For example, the electronic device may set a part of the storage space of the memory as the virtual memory, and may control access to the storage space of the memory set as the virtual memory to be performed through a virtual address (or logical address).

Meanwhile, the virtual memory may include a user area, which is a unique space of an application process, and a kernel area, which is a space shared by all application processes. In addition, the user area includes the stack area, which is a storage space for temporarily stored data such as local variables used by the application, the heap area which is a space dynamically allocated by the application, global variables used by the application, or Like static variables, it includes a data area, which is a space created when an application is executed and returned to the system when the application is terminated, and a code area, a space where an application's command (or code) is stored in the form of machine language. can do.

The above-described heap area of the virtual memory may include a native heap area and a java virtual machine (JVM) heap area, where the JVM heap area is a configuration file (eg, " AndroidManifest.xml" file), it can be determined according to the set value (eg "true" or "false" (default value)) of the size attribute (eg, defined as "largeHeap") of the heap area. For example, if the set value of the size attribute of the heap area is set to "true", the JVM heap area may be allocated with the maximum usable size (eg, 1 GB).

Since the existing electronic device determines the size of the heap area of the virtual memory according to the setting value of the size attribute of the heap area described in the setting file in the application package when the application is executed, the size of the heap area can be determined regardless of the actual usage. can In addition, the size of the heap area is initialized once when the application is executed, and it may be difficult to adjust thereafter. Accordingly, when a virtual memory corresponding to an application is allocated, memory allocation may fail due to insufficient memory space.

Various embodiments of the present disclosure may provide a virtual memory allocation method for determining a size of a heap area based on actual usage of the heap area when allocating a virtual memory corresponding to an application, and an electronic device supporting the same.

An electronic device according to various embodiments of the present disclosure includes a memory for storing an application, and a processor operatively connected to the memory, wherein the processor includes a memory for a virtual memory corresponding to the application during execution of the application. If the allocation fails, information indicating the failure of the memory allocation is set, and when the application is re-executed, if the set information exists, the size of the heap area included in the virtual memory is determined based on the set information, It may be configured to allocate the virtual memory including the heap area of the determined size.

Also, in the method of allocating a virtual memory of an electronic device according to various embodiments of the present disclosure, if memory allocation for a virtual memory corresponding to the application fails while an application stored in the memory of the electronic device is executed, the memory allocation An operation of setting information indicating failure, an operation of determining a size of a heap area included in the virtual memory based on the set information if the set information exists when the application is re-executed, and a heap area of the determined size Allocating the virtual memory including

According to various embodiments of the present disclosure, when the virtual memory corresponding to the application is allocated, the size of the heap area is determined based on the actual usage of the heap area, thereby maximizing the efficiency of the storage space of the virtual memory.

In addition, according to various embodiments of the present disclosure, it is possible to increase the stability of memory use by reducing the probability of a failure in the allocation of virtual memory.

In addition, various effects directly or indirectly identified through this document may be provided.

1 is a block diagram of an electronic device in a network environment according to various embodiments of the present disclosure;
2 is a diagram for explaining a configuration of an electronic device related to virtual memory allocation according to an embodiment of the present invention.
3 is a diagram for explaining a method of handling a failure in memory allocation to a virtual memory according to an embodiment of the present invention.
4 is a diagram for explaining a virtual memory allocation method according to an embodiment of the present invention.
5 is a diagram for explaining a method of setting information related to a failure in memory allocation to a virtual memory according to an embodiment of the present invention.
6 is a diagram for explaining a processing operation related to virtual memory allocation according to an embodiment of the present invention.
In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. For convenience of description, the sizes of the components shown in the drawings may be exaggerated or reduced, and the present invention is not necessarily limited to the illustrated ones.

1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments. Referring to FIG. 1 , in a network environment 100 , an electronic device 101 communicates with an electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199 . It may communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes a processor 120 , a memory 130 , an input module 150 , a sound output module 155 , a display module 160 , an audio module 170 , and a sensor module ( 176), interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module 196 , or an antenna module 197 may be included. In some embodiments, at least one of these components (eg, the connection terminal 178 ) may be omitted or one or more other components may be added to the electronic device 101 . In some embodiments, some of these components (eg, sensor module 176 , camera module 180 , or antenna module 197 ) are integrated into one component (eg, display module 160 ). can be

The processor 120, for example, executes software (eg, a program 140) to execute at least one other component (eg, a hardware or software component) of the electronic device 101 connected to the processor 120 . It can control and perform various data processing or operations. According to one embodiment, as at least part of data processing or operation, the processor 120 converts commands or data received from other components (eg, the sensor module 176 or the communication module 190 ) to the volatile memory 132 . may be stored in the volatile memory 132 , and may process commands or data stored in the volatile memory 132 , and store the result data in the non-volatile memory 134 . According to an embodiment, the processor 120 is the main processor 121 (eg, a central processing unit or an application processor) or a secondary processor 123 (eg, a graphic processing unit, a neural network processing unit) a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, when the electronic device 101 includes the main processor 121 and the sub-processor 123 , the sub-processor 123 may use less power than the main processor 121 or may be set to be specialized for a specified function. can The auxiliary processor 123 may be implemented separately from or as a part of the main processor 121 .

The auxiliary processor 123 is, for example, on behalf of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or the main processor 121 is active (eg, executing an application). ), together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display module 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to an embodiment, the coprocessor 123 (eg, an image signal processor or a communication processor) may be implemented as part of another functionally related component (eg, the camera module 180 or the communication module 190). have. According to an embodiment, the auxiliary processor 123 (eg, a neural network processing device) may include a hardware structure specialized for processing an artificial intelligence model. Artificial intelligence models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself on which artificial intelligence is performed, or may be performed through a separate server (eg, the server 108). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but in the above example not limited The artificial intelligence model may include a plurality of artificial neural network layers. Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the above example. The artificial intelligence model may include, in addition to, or alternatively, a software structure in addition to the hardware structure.

The memory 130 may store various data used by at least one component of the electronic device 101 (eg, the processor 120 or the sensor module 176 ). The data may include, for example, input data or output data for software (eg, the program 140 ) and instructions related thereto. The memory 130 may include a volatile memory 132 or a non-volatile memory 134 .

The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system 142 , middleware 144 , or an application 146 .

The input module 150 may receive a command or data to be used in a component (eg, the processor 120 ) of the electronic device 101 from the outside (eg, a user) of the electronic device 101 . The input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).

The sound output module 155 may output a sound signal to the outside of the electronic device 101 . The sound output module 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback. The receiver may be used to receive an incoming call. According to one embodiment, the receiver may be implemented separately from or as part of the speaker.

The display module 160 may visually provide information to the outside (eg, a user) of the electronic device 101 . The display module 160 may include, for example, a control circuit for controlling a display, a hologram device, or a projector and a corresponding device. According to an embodiment, the display module 160 may include a touch sensor configured to sense a touch or a pressure sensor configured to measure the intensity of a force generated by the touch.

The audio module 170 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 170 acquires a sound through the input module 150 or an external electronic device (eg, a sound output module 155 ) directly or wirelessly connected to the electronic device 101 . A sound may be output through the electronic device 102 (eg, a speaker or headphones).

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, user state), and generates an electrical signal or data value corresponding to the sensed state. can do. According to one embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 177 may support one or more designated protocols that may be used by the electronic device 101 to directly or wirelessly connect with an external electronic device (eg, the electronic device 102 ). According to an embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102 ). According to an embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 179 may convert an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 may capture still images and moving images. According to an embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 may manage power supplied to the electronic device 101 . According to an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101 . According to one embodiment, battery 189 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module 190 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (eg, the electronic device 102, the electronic device 104, or the server 108). It can support establishment and communication performance through the established communication channel. The communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (eg, a cellular communication module, a short-range communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (eg, : It may include a LAN (local area network) communication module, or a power line communication module). A corresponding communication module among these communication modules is a first network 198 (eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (eg, legacy It may communicate with the external electronic device 104 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (eg, a telecommunication network such as a LAN or a WAN). These various types of communication modules may be integrated into one component (eg, a single chip) or may be implemented as a plurality of components (eg, multiple chips) separate from each other. The wireless communication module 192 uses the subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199 . The electronic device 101 may be identified or authenticated.

The wireless communication module 192 may support a 5G network after a 4G network and a next-generation communication technology, for example, a new radio access technology (NR). NR access technology includes high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency) -latency communications)). The wireless communication module 192 may support a high frequency band (eg, mmWave band) to achieve a high data rate, for example. The wireless communication module 192 includes various technologies for securing performance in a high-frequency band, for example, beamforming, massive multiple-input and multiple-output (MIMO), all-dimensional multiplexing. It may support technologies such as full dimensional MIMO (FD-MIMO), an array antenna, analog beam-forming, or a large scale antenna. The wireless communication module 192 may support various requirements specified in the electronic device 101 , an external electronic device (eg, the electronic device 104 ), or a network system (eg, the second network 199 ). According to an embodiment, the wireless communication module 192 may include a peak data rate (eg, 20 Gbps or more) for realizing eMBB, loss coverage (eg, 164 dB or less) for realizing mMTC, or U-plane latency for realizing URLLC ( Example: downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less).

The antenna module 197 may transmit or receive a signal or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern. According to an embodiment, the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is connected from the plurality of antennas by, for example, the communication module 190 . can be selected. A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna. According to some embodiments, other components (eg, a radio frequency integrated circuit (RFIC)) other than the radiator may be additionally formed as a part of the antenna module 197 .

According to various embodiments, the antenna module 197 may form a mmWave antenna module. According to one embodiment, the mmWave antenna module comprises a printed circuit board, an RFIC disposed on or adjacent to a first side (eg, bottom side) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, an array antenna) disposed on or adjacent to a second side (eg, top or side) of the printed circuit board and capable of transmitting or receiving signals of the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and a signal ( eg commands or data) can be exchanged with each other.

According to an embodiment, the command or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external electronic devices 102 or 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or a part of operations executed in the electronic device 101 may be executed in one or more external electronic devices 102 , 104 , or 108 . For example, when the electronic device 101 is to perform a function or service automatically or in response to a request from a user or other device, the electronic device 101 may perform the function or service itself instead of executing the function or service itself. Alternatively or additionally, one or more external electronic devices may be requested to perform at least a part of the function or the service. One or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit a result of the execution to the electronic device 101 . The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an Internet of things (IoT) device. Server 108 may be an intelligent server using machine learning and/or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199 . The electronic device 101 may be applied to an intelligent service (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.

2 is a diagram for explaining a configuration of an electronic device related to virtual memory allocation according to an embodiment of the present invention.

Referring to FIG. 2 , an electronic device 200 (eg, the electronic device 101 of FIG. 1 ) includes a memory 210 (eg, the memory 130 of FIG. 1 ) and a processor 230 (eg, the electronic device 101 of FIG. 1 ). processor 120). However, the configuration of the electronic device 200 is not limited thereto. According to various embodiments, the electronic device 200 may further include at least one other component in addition to the above-described components. For example, the electronic device 200 may further include at least one of the components illustrated in FIG. 1 .

The memory 210 may store various data used by at least one component of the electronic device 200 . According to an embodiment, the memory 210 may store an application 211 that may be executed by the processor 230 .

The processor 230 may control at least one other component of the electronic device 200 and may perform various data processing or operations. According to an embodiment, the processor 230 may execute the application 211 stored in the memory 210 . In the process of executing the application 211 , the processor 230 uses the virtual memory 250 to more efficiently use the limited storage space of the memory 210 to actually physically exist memory ( 210) can provide more storage space. For example, the processor 230 sets a part of the storage space of the memory 210 as the virtual memory 250 , and provides access to the storage space of the memory 210 set as the virtual memory 250 as a virtual address. (or logical address) can be controlled to be performed.

The virtual memory 250 may include a user area, which is a unique space of a process of a specific application 211 , and a kernel area, which is a space shared by processes of all applications 211 . Here, the process may represent a program operated in one system, that is, the electronic device 200 . The user area includes a stack area 251 that is a storage space for data temporarily stored such as local variables used by the application 211 , a heap area 253 which is a space dynamically allocated by the application 211 , and an application ( A data area 255, which is a space created when the application 211 is executed, and returned to the system when the application 211 is terminated, such as a global variable or static variable used by the 211, and a command (or code) of the application 211 ) may include a code area 257 that is a space in which machine language is stored.

According to an embodiment, when the processor 230 executes the application 211 , it is described in a setting file of the application 211 (eg, an “AndroidManifest.xml” file included in the package of the application 211 ). Virtual memory (eg, "true" or "false" (default value)) corresponding to the application 211 according to the set value (eg, "true" or "false" (default value)) of the size attribute (eg, attribute defined as "largeHeap") of the heap area 253 The size of the heap area 253 of 250 may be determined. For example, when the set value of the size attribute of the heap area 253 is set to "true", the processor 230 determines the maximum usable size of the JVM heap area among the heap areas 253 (eg, 1 GB). ) can be assigned.

According to an embodiment, when the processor 230 executes the application 211 , information indicating a failure in memory allocation to the virtual memory 250 corresponding to the application 211 (hereinafter referred to as a profile) is displayed. If present, the size of the heap area 253 of the virtual memory 250 may be determined based on the profile. In this case, the processor 230 may ignore the setting value of the size attribute of the heap area 253 described in the setting file of the application 211 . For example, if memory allocation for the virtual memory 250 corresponding to the application 211 fails while the processor 230 is executing the application 211 , information indicating the failure of the memory allocation, that is, the profile can be set, and the set profile can be stored in the memory 210 . According to an embodiment, when the profile is not stored in the memory 210 , the processor 230 may newly create the profile, and when the profile is stored in the memory 210 , The processor 230 may modify (or change) the stored profile. According to an embodiment, the profile may be stored in the memory 210 in the form of a file. Also, when the profile exists, the processor 230 may determine the size of the heap area 253 of the virtual memory 250 based on the profile when the application 211 is re-executed.

According to an embodiment, when the memory allocation fails, the processor 230 may include the actual usage of the heap area 253 according to the execution of the application 211 in the profile. For example, when the memory allocation fails, the processor 230 may check information on the actual usage of the heap area 253 based on a time point at which the memory allocation fails and record the information in the profile. Also, when the virtual memory 250 is allocated, the processor 230 may determine the size of the heap area 253 based on the actual usage of the heap area 253 recorded in the profile. As the size of the heap area 253 is determined based on the actual usage of the heap area 253 recorded in the profile, the efficiency of the storage space of the virtual memory 250 can be maximized, and the virtual A failure probability of memory allocation for the memory 250 may be reduced.

According to an embodiment, the actual usage of the heap area 253 is based on the checked usage of the heap area 253 when a failure signal for memory allocation due to out of memory in the virtual memory occurs. can be calculated as

According to an embodiment, the size of the heap area 253 may be set as a step value indicating size ranges divided by a specified number. For example, the size of the heap area 253 may be divided into a first stage value (eg, 256 MB), a second stage value (eg, 384 MB), and a third stage value (eg, 512 MB). The first step value may be the minimum value of the size of the heap area 253, and may be set when the actual usage of the heap area 253 is included in the size range (eg, 0 to 256 MB) less than the minimum value. have. Similarly, the second step value may be set when the actual usage of the heap area 253 is greater than the minimum value and is included in a size range (eg, 257 to 384 MB) less than or equal to the second step value, and the third step The value may be set when the actual usage of the heap area 253 is greater than the second step value and is included in the size range (eg, 385 to 512 MB) less than or equal to the third step value. Here, the number of differentiated step values is not limited thereto. The number of the differentiated step values may be determined according to the maximum usable size of the heap area 253 , and may be at least two or more.

According to an embodiment, the processor 230 may increase or decrease the size of the heap area 253 according to the type of failure in memory allocation for the virtual memory 250 . For example, when the memory allocation failure is the first failure that occurs when a storage space for a region other than the heap region 253 among regions included in the virtual memory 250 is insufficient, the processor 230 may reduce the size of the heap region 253 . To this end, the processor 230 may include information for reducing the size of the heap area 253 in the profile. According to an embodiment, the processor 230 may record information for setting the size of the heap area 253 to a value that is at least one step lower in the profile. For example, when the current size of the heap region 253 is set to the third stage value, the processor 230 sets the size of the heap region 253 in the profile to the second stage value or the second stage value. You can record information that causes it to be set to a one-step value. As another example, when the current size of the heap region 253 is set to the second stage value, the processor 230 sets the size of the heap region 253 to the first stage value in the profile. You can record information that allows you to set it.

As another example, when the memory allocation failure is a second failure that occurs when a storage space for the heap area 253 among areas included in the virtual memory 250 is insufficient, the processor 230 performs the The size of the region 253 may be increased. To this end, the processor 230 may include information for increasing the size of the heap area 253 in the profile. According to an embodiment, the processor 230 may record information for setting the size of the heap area 253 to a value that is at least one step higher in the profile. For example, when the current size of the heap region 253 is set to the first stage value, the processor 230 sets the size of the heap region 253 to the second stage value or the second stage value in the profile. You can record information that causes it to be set to a three-level value. As another example, when the current size of the heap region 253 is set to the second stage value, the processor 230 sets the size of the heap region 253 to the third stage value in the profile. You can record information that allows you to set it.

The first failure is caused by, for example, a lack of storage space (eg, "out of memory (ENOMEM)") that occurs when a function that performs a memory mapping function for a file (eg, mmap() function) is used. may indicate failure. The second failure may indicate, for example, a failure due to insufficient storage space in the JVM heap area (eg, “JVM out of memory (OOM)”).

According to an embodiment, when the first failure occurs, the processor 230 may determine whether to change the size of the heap area 253 based on the actual usage of the heap area 253 . If the actual usage of the heap area 253 is smaller than the step value for reducing the size of the heap area 253 according to the occurrence of the first failure, the processor 230 determines the size of the heap area 253 . may be set as the step value. For example, if the current size of the heap area 253 is set to the third step value, and the actual usage of the heap area 253 is less than the second step value, the first failure occurs. Accordingly, the size of the heap region 253 may be set to the value of the second step. As another example, if the actual usage of the heap area 253 is smaller than the first step value in a state where the current size of the heap area 253 is set to the third step value, the first failure The size of the heap region 253 according to the occurrence may be set to the second stage value or the first stage value.

According to an embodiment, the processor 230 determines that when both the history of occurrence of the first failure and the history of occurrence of the second failure exist in a state in which the size of the heap region 253 is the same, the heap region ( 253) may not change the size. For example, when the first failure and the second failure occur while the size of the heap area 253 is set to the second stage value, the processor 230 maintains the size of the heap area 253 . can do it

According to an embodiment, the processor 230 determines that when both the history of occurrence of the first failure and the history of occurrence of the second failure exist in a state where the size of the heap area 253 is not the same, the heap Whether to change the size of the heap area 253 may be determined based on the actual usage of the area 253 . When the processor 230 has a settable size between the size of the heap area 253 at the time when the first failure occurs and the size of the heap area 253 at the time when the second failure occurs , it is determined whether the actual usage of the heap area 253 is smaller than the settable size, and when the actual usage of the heap area 253 is smaller than the settable size, the size of the heap area 253 is set It can be set to any possible size. For example, if the second failure occurs when the size of the heap region 253 is the first stage value, and the first failure occurs when the size of the heap region 253 is the third stage, The processor 230 checks whether the actual usage of the heap area 253 is less than the value of the second step between the first step value and the third step value, and the actual amount of the heap area 253 is When the amount used is smaller than the value of the second step, the size of the heap area 253 may be set as the value of the second step. For another example, the second failure occurs when the size of the heap region 253 is the first stage value, and the first failure occurs when the size of the heap region 253 is the second stage , since there is no settable step value between the first step value and the second step value, the processor 230 considers the actual usage of the heap area 253, may be set as the value of the second step.

In the above description, the case in which the size of the heap area 253 is set to a step value indicating size ranges divided by a specified number has been described, but the present invention is not limited thereto. According to various embodiments, the processor 230 may set the size of the heap area 253 to a value larger than a specified size or more than the actual usage of the heap area 253 . In this case, the processor 230 may set the size of the heap area 253 to a size corresponding to the unit throughput (eg, page size) of the memory 210 .

According to an embodiment, the size of the heap area 253 may be a memory size value (eg, 0 to 1 GB) calculated based on actual usage. For example, the size of the heap area 253 is determined by adding a margin value (eg, a specified size value or a value obtained by multiplying the size of the currently allocated heap area 253 by a specified ratio) to the actual usage or actual usage. It may be a calculated size.

According to an embodiment, when the memory allocation failure is the first failure that occurs when a storage space for a region other than the heap region 253 among regions included in the virtual memory 250 is insufficient, the processor Reference numeral 230 records information for setting the size of the heap area 253 to a value smaller by a specified or calculated size in the profile. For example, when the current size of the heap area 253 is set to a first set value, the processor 230 sets the size of the heap area 253 in the profile to a second value smaller than the first set value. It is possible to record information to set it as a set value.

According to an embodiment, when the failure of the memory allocation is the second failure occurring when the storage space for the heap area 253 among the areas included in the virtual memory 250 is insufficient, the processor 230 may record information for setting the size of the heap area 253 to a value as large as a specified or calculated size in the profile. For example, when the current size of the heap area 253 is set to a first set value, the processor 230 sets the size of the heap area 253 in the profile to a second value greater than the first set value. It is possible to record information to set it as a set value.

According to an embodiment, when the first failure occurs, the processor 230 may transmit a signal indicating the occurrence of the first failure to a process related to the execution of the application 211 . According to an embodiment, the signal may include a result value (eg, a result value of failure or success) of an independently executable SW module during internal operation of the process. The SW module may be a module that performs a function of setting a heap area. In the case of the first failure, since the same type of failure (first failure) may occur several times after being generated once, the processor 230 transmits the signal and then performs a specified number of times (eg, 50 When other first failures of the same type occur, it is possible to control so that signals indicating occurrence of the other first failures are not transmitted to the process. In addition, when another first failure occurs after the other first failures of the specified number of times, the processor 230 may transmit a newly generated signal indicating the occurrence of the other first failure to the process. have. According to an embodiment, the processor 230 may include information on the number of signals indicating the occurrence of the first failure transmitted to the process in the profile. For example, the processor 230 may record the number of signals indicating the occurrence of the first failure in the profile.

According to an embodiment, when the number of signals indicating occurrence of the first failure included in the profile exceeds a specified value (eg, three times), the processor 230 determines the size of the heap area 253. You can decide whether to change or not. For example, when the number of signals indicating the occurrence of the first failure exceeds the specified value, the processor 230 is configured to, based on the actual usage of the heap area 253 and the history of occurrence of the second failure, Whether to change the size of the region 253 may be determined.

According to an embodiment, the information included in the profile, that is, the information recorded in the profile, includes information on whether the size of the heap area 253 is changed (eg, one of size maintenance, size reduction, and size increase). value), the size change value of the heap area 253 (eg, a step value to change or a size value to change), the actual usage of the heap area 253, the number of signals indicating the occurrence of the first failure, and the It may include at least one of the number of occurrences of the second failure.

As described above, according to various embodiments, the electronic device (eg, the electronic device 200 of FIG. 2 ) stores an application (eg, the application 211 of FIG. 2 ) in a memory (eg, the memory of FIG. 2 ) 210), and a processor operatively connected to the memory (eg, the processor 230 of FIG. 2 ), wherein the processor includes a virtual memory corresponding to the application (eg, FIG. 2 ) during execution of the application If the memory allocation to the virtual memory 250 of the , information indicating the failure of the memory allocation is set, and when the application is re-executed, if the set information exists, the information indicating the failure of the memory allocation is stored in the virtual memory based on the set information. The size of the included heap area (eg, the heap area 253 of FIG. 2 ) may be determined and the virtual memory including the heap area of the determined size may be allocated.

According to various embodiments, the processor may be set to ignore a setting value of the size attribute of the heap area described in a setting file of the application if the set information exists when the application is re-executed.

According to various embodiments, the processor may be configured to include the actual usage of the heap area according to the execution of the application in the set information, and to determine the size of the heap area based on the actual usage of the heap area. have.

According to various embodiments, the size of the heap area is set to a step value representing size ranges divided by a specified number, and the processor represents, among the size ranges, a size range in which the actual usage of the heap area is included. The size of the heap area can be set as a value.

According to various embodiments, the failure of the memory allocation may include a first failure occurring when a storage space for a region other than the heap region among regions included in the virtual memory is insufficient.

According to various embodiments, when the first failure occurs, the processor may be configured to include information for reducing the size of the heap area in the set information.

According to various embodiments, when the first failure occurs, the processor may be configured to transmit a signal indicating the occurrence of the first failure to a process related to the execution of the application.

According to various embodiments, the processor controls not to transmit signals indicating the occurrence of the other first failures to the process, if other first failures of a specified number of times occur after the signal is transmitted, After the occurrence of 1 failures, when another first failure occurs, a signal indicating the occurrence of the another first failure is transmitted to the process, and when the number of the signals received by the process exceeds a specified value, the It can be set to determine whether to change the size of the heap area.

According to various embodiments, the failure of the memory allocation may include a second failure occurring when a storage space for the heap area among the areas included in the virtual memory is insufficient.

According to various embodiments, when the second failure occurs, the processor may be configured to include information for increasing the size of the heap area in the set information.

3 is a diagram for explaining a method of handling a failure in memory allocation to a virtual memory according to an embodiment of the present invention.

Referring to FIG. 3 , in operation 310 , the processor (eg, the processor 230 of FIG. 2 ) of the electronic device (eg, the electronic device 200 of FIG. 2 ) performs a virtual memory (eg, the virtual memory 250 of FIG. 2 ). )), it can be determined whether memory allocation has failed. The failure of memory allocation for the virtual memory is, for example, the first failure due to lack of storage space that occurs when a function (eg, mmap()) that performs a memory mapping function for a file is used, and the JVM heap area. may include a second failure due to a lack of storage space. The first failure and the second failure may occur in the form of a system event. The first failure is, for example, a failure value (eg, "MAP_FAILED") is returned as a result of calling the mmap() function, and an identification value for failure (eg "errno") is a value indicating insufficient storage space. It can represent a state containing (eg "ENOMEM(out of memory)"). Also, the second failure may indicate, for example, a state in which an event indicating insufficient storage space of the JVM heap area (eg, "JVM out of memory (OOM)") has occurred. For example, the second failure occurs when the application 211 is executed or when a java object cannot be allocated to the heap area due to insufficient storage space of the heap area during execution, an event (eg, "out of memory)”) can indicate the generated state. That is, the first failure may occur when a storage space for a region other than a heap region (eg, the heap region 253 in FIG. 2 ) among regions included in the virtual memory is insufficient, and the second failure It may be generated when a storage space for the heap area among areas included in the virtual memory is insufficient.

If it is determined that the memory allocation to the virtual memory has failed, in operation 330 , the processor may set information indicating the failure of the memory allocation to the virtual memory (hereinafter, referred to as a profile). Also, the processor may store the set profile in a memory (eg, the memory 210 of FIG. 2 ). According to an embodiment, when the profile is not stored in the memory, the processor may create a new profile, and if the profile is stored in the memory, the processor modifies ( or change). According to an embodiment, the profile may be stored in the memory in the form of a file.

According to an embodiment, the information included in the profile, that is, information recorded in the profile, is information on whether the size of a heap area included in the virtual memory (eg, the heap area 253 in FIG. 2 ) is changed. (eg, a value indicating one of maintaining size, decreasing size, and increasing size), the size change value of the heap area (eg, the step value to change or the size value to change), the actual usage of the heap area, the occurrence of the first failure It may include at least one of the number of signals indicating , and the number of occurrences of the second failure.

According to an embodiment, when the memory allocation fails, the processor may include the actual usage of the heap area according to the execution of an application (eg, the application 211 of FIG. 2 ) in the profile. For example, the processor may record the actual usage of the heap area in the profile.

According to an embodiment, when the failure of the memory allocation is a first failure that occurs when a storage space for a region other than the heap region among regions included in the virtual memory is insufficient, the processor adds the heap to the profile. Information for reducing the size of the region may be included. For example, the processor may record information for setting the size of the heap area to a value lower by at least one step in the profile. In this case, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating a size reduction.

According to an embodiment, when the failure of the memory allocation is a second failure that occurs when a storage space for the heap region among regions included in the virtual memory is insufficient, the processor includes the size of the heap region in the profile. You can include information to increase For example, the processor may record information for setting the size of the heap area to a value that is at least one step higher in the profile. In this case, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating an increase in size.

According to an embodiment, when the first failure occurs, the processor may set a size change value of the heap area included in the profile based on the actual usage of the heap area. For example, the processor may set the size of the heap area to the step value when the actual usage of the heap area is smaller than the step value for reducing the size of the heap area according to the occurrence of the first failure . In this case, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating a size reduction.

According to an embodiment, when both the first failure occurrence history and the second failure occurrence history exist in a state in which the size of the heap region is the same, the processor determines the size of the heap region included in the profile The change value can be set to zero or deleted. For example, when both the first failure and the second failure occur in a state in which the size of the heap area is the same, the processor maintains the size of information on whether the size of the heap area included in the profile is changed. It can be set to the indicated value.

According to an embodiment, when both the first failure occurrence history and the second failure occurrence history exist in a state in which the size of the heap region is not the same, the processor is based on the actual usage of the heap region Accordingly, information regarding whether to change the size of the heap area can be set. For example, when a settable size exists between the size of the heap area at the time when the first failure occurs and the size of the heap area at the time when the second failure occurs, the processor It is determined whether the actual usage amount is smaller than the settable size, and when the actual usage amount of the heap area is smaller than the settable size, the size of the heap area may be set to the settable size. In this case, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating an increase in size. For another example, if there is no settable size between the size of the heap area at the time when the first failure occurs and the size of the heap area at the time when the second failure occurs, the processor In consideration of the actual usage of the area, the size of the heap area may be set to a value larger than the size of the existing heap area. Also in this case, the processor may set the information on whether the size of the heap area included in the profile is changed as a value indicating an increase in size.

According to an embodiment, when the first failure occurs, the processor may transmit a signal indicating the occurrence of the first failure to a process related to the execution of the application, and after transmitting the signal, the same number of times When other first failures of a different kind occur, it is possible to control so that signals indicating occurrence of the other first failures are not transmitted to the process. In addition, when another first failure occurs after the other first failures of the specified number of times, the processor may transmit a signal indicating the occurrence of the new first failure to the process. In this case, the processor may include information on the number of signals indicating the occurrence of the first failure transmitted to the process in the profile. For example, the processor may record the number of signals indicating the occurrence of the first failure in the profile. In addition, when the number of signals indicating occurrence of the first failure included in the profile exceeds a specified value, the processor displays information on whether or not to change the size of the heap region included in the profile to indicate size reduction It can be set as a value.

According to an embodiment, when the second failure occurs, the processor may record the number of occurrences of the second failure included in the profile. For example, when the second failure occurs, the processor may increase the number of occurrences of the second failure included in the profile.

4 is a diagram for explaining a virtual memory allocation method according to an embodiment of the present invention.

Referring to FIG. 4 , in operation 410 , the processor (eg, the processor 230 of FIG. 2 ) of the electronic device (eg, the electronic device 200 of FIG. 2 ) performs a virtual memory (eg, the virtual memory 250 of FIG. 2 ). )), it can be determined whether information indicating the failure of memory allocation (hereinafter referred to as a profile) exists. For example, when an application (eg, the application 211 of FIG. 2 ) stored in a memory (eg, the memory 210 of FIG. 2 ) is executed, the processor may determine whether a profile stored in the memory exists.

If it is determined that the profile does not exist, in operation 430, the processor performs a heap area (eg, in FIG. 2 ) based on a setting file of the application (eg, an “AndroidManifest.xml” file included in the package of the application). The size of the heap area 253) may be determined. For example, according to the set value (eg, "true" or "false" (default value)) of the size attribute of the heap area (eg, the attribute defined as "largeHeap") described in the configuration file of the application, the processor The size of the heap area of the virtual memory corresponding to the application may be determined. For example, when the set value of the size attribute of the heap area is set to "true", the processor may allocate the JVM heap area among the heap areas to a maximum usable size (eg, 1 GB).

If it is determined that the profile exists, the processor may determine the size of the heap area based on the profile in operation 450 . According to an embodiment, the processor may determine the size of the heap area based on the actual usage of the heap area included in the profile. For example, the processor may determine the size of the heap area as a value larger than a specified size or more than the actual usage of the heap area. According to an embodiment, the processor may determine the size of the heap region based on a size change value of the heap region included in the profile. For example, the processor may determine the size of the heap area using the size change value of the heap area. Here, the size change value of the heap area is a value set to a value larger than a specified size or more than the actual usage of the heap area, or step values representing size ranges in which the size of the heap area is divided by a specified number (eg, first a step value, a second step value, or a third step value).

According to an embodiment, the processor may maintain the size of the heap region when the information on whether the size of the heap region included in the profile is set to a value indicating size maintenance. According to another embodiment, when the information on whether the size of the heap area included in the profile is changed is set to a value indicating a size reduction, the processor is configured to use the size change value of the heap area included in the profile. The size of the heap area can be reduced. According to another embodiment, when the information on whether the size of the heap area included in the profile is changed is set to a value indicating an increase in size, the processor is configured to change the size of the heap area included in the profile. The size of the heap area may be increased.

When the size of the heap area is determined, the processor may set (or allocate) the virtual memory including the heap area of the determined size in operation 470 .

5 is a diagram for explaining a method of setting information related to a failure in memory allocation to a virtual memory according to an embodiment of the present invention.

Referring to FIG. 5 , the processor (eg, the processor 230 of FIG. 2 ) of the electronic device (eg, the electronic device 200 of FIG. 2 ) corresponds to a virtual memory (eg, the virtual memory 250 of FIG. 2 ). According to the type of memory allocation failure, the size of the heap area included in the virtual memory (eg, the heap area 253 of FIG. 2 ) may be increased or decreased. The failure of memory allocation for the virtual memory is, for example, a first failure due to a lack of storage space that occurs when a function performing a memory mapping function for a file is used, and a first failure due to a lack of storage space in the JVM heap area. A second failure may be included. The first failure may occur when a storage space for a region other than the heap region among regions included in the virtual memory is insufficient, and the second failure may occur in the heap region among regions included in the virtual memory. It may occur when there is insufficient storage space for storage.

In operation 510 , the processor may determine whether the failure of the memory allocation is a failure (the second failure) due to insufficient storage space for the heap area.

When it is determined that the failure of the memory allocation is not a failure due to a lack of storage space for the heap region, that is, the failure of the memory allocation is a failure due to a lack of storage space for a region other than the heap region (the first failure), in operation 530 , the processor may set information indicating failure of memory allocation to the virtual memory (hereinafter, referred to as a profile) to include information for reducing the size of the heap region. For example, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating a size reduction. In addition, the processor sets the size change value of the heap area included in the profile to a value smaller than the current size of the heap area, or sets the value at least one step lower than the step value set as the current size of the heap area. can

When it is determined that the failure of the memory allocation is a failure due to a lack of storage space for the heap area, that is, when the failure of the memory allocation is a failure (the second failure) due to a lack of storage space for the heap area , the processor may set the profile to include information for increasing the size of the heap area in operation 550 . For example, the processor may set information on whether to change the size of the heap area included in the profile as a value indicating an increase in size. In addition, the processor sets the size change value of the heap area included in the profile to a value larger than the current size of the heap area, or sets a step value at least one step higher than the step value set as the current size of the heap area. can

In the above-described operation 510, the processor determines whether the failure of the memory allocation is a failure (the second failure) due to insufficient storage space for the heap area, but is not limited thereto. In some embodiments, in operation 510 , the processor may determine whether the failure of the memory allocation is a failure (the first failure) due to insufficient storage space for a region other than the heap region. Likewise in this case, the processor may perform operation 530 if it is determined that the failure of memory allocation is a failure due to insufficient storage space for a region other than the heap region, and the memory allocation failure occurs other than the heap region. If it is determined that the failure is not due to insufficient storage space for the area of , operation 550 may be performed.

If the profile is set to include information for reducing or increasing the size of the heap area, the processor may store the set profile in operation 570 . For example, the processor may store the profile in a memory (eg, the memory 210 of FIG. 2 ). According to an embodiment, the processor may store the profile in the memory in the form of a file.

6 is a diagram for explaining a processing operation related to virtual memory allocation according to an embodiment of the present invention.

Referring to FIG. 6 , the electronic device (eg, the electronic device 200 of FIG. 2 ) includes an application 610 (eg, the application 211 of FIG. 2 ), a virtual machine 630 , and a heap area setting module 650 . ) may be included. The virtual machine 630 (eg, a java virtual machine (JVM)) is a program executed by a processor (eg, the processor 230 of FIG. 2 ) of the electronic device, and is an operating system or an application program. An installation and execution environment of (eg, the application 610 ) may be provided. The virtual machine 630 detects the failure of the virtual memory setting module 631 for allocating the virtual memory (eg, the virtual memory 250 of FIG. 2 ) corresponding to the application 610 , the memory allocation for the virtual memory. A memory allocation failure detection module 633 for detecting, a signal processing module 635 for processing a signal indicating occurrence of the memory allocation failure, and information indicating a failure of memory allocation for the virtual memory (hereinafter, a profile 651 ) ) may include a profile setting module 637 for setting. The heap area setting module 650 may determine the size of a heap area (eg, the heap area 253 of FIG. 2 ) of the virtual memory corresponding to the application 610 .

When an execution request for the application 610 occurs, the virtual machine 630 may execute the application 610 in operation 671 . During the execution of the application 610 , the virtual memory setting module 631 of the virtual machine 630 may allocate a virtual memory corresponding to the application 610 in operation 672 . According to an embodiment, the virtual memory setting module 631 is configured to be configured based on the setting file 611 of the application 610 (eg, "AndroidManifest.xml" file included in the package of the application 610). You can determine the size of the heap area of virtual memory. For example, the virtual memory setting module 631 may set a value (eg, "true" or "false") of a size attribute (eg, a attribute defined as "largeHeap") of the heap area described in the setting file 611 . (default value)), the size of the heap area of the virtual memory may be determined.

When a failure (first failure) occurs due to insufficient storage space for a region other than the heap region among regions included in the virtual memory while the application 610 is running, the memory of the virtual machine 630 is The allocation failure detection module 633 may detect the failure in operation 673 . Detecting the failure may mean detecting a system event that occurs when memory allocation fails due to insufficient storage space. In addition, in operation 674 , the memory allocation failure detection module 633 transmits a memory allocation failure signal (a signal indicating occurrence of a first failure) according to the insufficient storage space to the signal processing module 635 of the virtual machine 630 . ) can be transmitted. According to an embodiment, the memory allocation failure detection module 633 is configured to detect other failures (first failures) of the same type a specified number of times (eg, 50 times) after the transmission of the failure signal. Failure signals indicating occurrence may not be transmitted to the signal processing module 635 . In addition, when the memory allocation failure detection module 633 detects another failure of the same type (first failure) after detecting other failures of the same type for the specified number of times, a failure indicating occurrence of a newly detected failure A signal may be transmitted to the signal processing module 635 . Upon receiving the failure signal, the signal processing module 635 may execute the profile setting module 637 in operation 674-1.

When the profile setting module 637 is executed, the profile setting module 637 may set the profile 651 corresponding to the application 610 in operation 675 . If the profile 651 is not stored, the profile setting module 637 may newly create the profile 651, and if the profile 651 is stored, the profile setting module 637 may modify (or change) the stored profile 651 . The profile setting module 637 may record the number (or number of times) of the reception of the failure signal (the number of failure signals indicating the occurrence of the first failure) in the profile 651 in response to the reception of the failure signal. have.

When the number of receptions of the failure signal exceeds a specified value (eg, three times), the profile setting module 637 may set the profile 651 in operation 675 - 1 . For example, the profile setting module 637 may set information on whether to change the size of the heap area included in the profile 651 to a value indicating a size reduction.

When a failure (second failure) occurs due to a lack of storage space for the heap area among the areas included in the virtual memory, the profile setting module 637 generates the profile 651 in operation 675-2. The number of occurrences of failures due to insufficient storage space for the heap area may be recorded. Also, the profile setting module 637 may set information on whether to change the size of the heap area included in the profile 651 as a value indicating an increase in size. Also, the profile setting module 637 may record the actual usage of the heap area in the profile 651 .

According to an embodiment, when the number of reception of the failure signal exceeds the specified value, the profile setting module 637 may check the number of occurrences of failure due to insufficient storage space for the heap area. In consideration of the number of occurrences of failures due to insufficient storage space for the heap area, the profile setting module 637 may determine whether to change the size of the heap area. When it is determined to change the size of the heap region, the profile setting module 637 may set information on whether to change the size of the heap region in the profile 651 . Also, the profile setting module 637 may set a size change value of the heap area in the profile 651 .

When a re-execution request for the application 610 occurs, the virtual machine 630 may re-execute the application 610 in operation 676 . In the process of re-executing the application 610, the virtual memory setting module 631 allocates a virtual memory corresponding to the application 610. At this time, if the profile 651 exists (the profile 651) is stored), the heap area setting module 650 may determine the size of the heap area of the virtual memory based on the profile 651 in operation 677 . For example, the heap area setting module 650 may set (or change) the size of the heap area based on a size change value of the heap area recorded in the profile 651 . For example, the setting value of the size attribute of the heap area described in the setting file 611 of the application 610 may be ignored. According to an embodiment, after the size of the heap area of the virtual memory is determined based on the profile 651 , the heap area setting module 650 may reset information recorded in the profile 651 . . In some embodiments, the heap area setting module 650 may reset information other than the size change value of the heap area recorded in the profile 651 .

According to various embodiments, the various embodiments disclosed in this document may be applied not only to a Java virtual machine, but also to a virtual machine implemented in a Windows operating system such as a common language runtime (CLR).

As described above, according to various embodiments, the virtual memory allocation method of the electronic device (eg, the electronic device 200 of FIG. 2 ) is stored in the memory of the electronic device (eg, the memory 210 of FIG. 2 ). If memory allocation for a virtual memory corresponding to the application (eg, the virtual memory 250 of FIG. 2 ) fails during execution of a stored application (eg, the application 211 of FIG. 2 ), it indicates the failure of the memory allocation. In an operation of setting information (eg, operation 330 of FIG. 3 ), when the application is re-executed, if the set information exists, a heap area included in the virtual memory (eg, the heap area of FIG. 2 ) based on the set information (253)), determining the size (eg, operation 450 of FIG. 4), and allocating the virtual memory including the heap region of the determined size (eg, operation 470 of FIG. 4). have.

According to various embodiments, the operation of determining the size of the heap region may include an operation of ignoring a setting value of the size attribute of the heap region described in a setting file of the application if the set information exists.

According to various embodiments, the setting of the information indicating the failure of the memory allocation includes including the actual usage of the heap area according to the execution of the application in the set information, and determining the size of the heap area. The determining may include determining the size of the heap area based on the actual usage of the heap area.

According to various embodiments, the size of the heap area is set to a step value indicating a size range divided by a specified number, and the operation of determining the size of the heap area includes the actual usage of the heap area among the size ranges. It may include an operation of setting the size of the heap area to a step value indicating the included size range.

According to various embodiments, the failure of the memory allocation may include a first failure occurring when a storage space for a region other than the heap region among regions included in the virtual memory is insufficient.

According to various embodiments, the setting of the information indicating the failure of the memory allocation may include, when the first failure occurs, including information for reducing the size of the heap area in the set information (eg, FIG. 5 ) of operation 530).

According to various embodiments, the method of allocating the virtual memory may further include, when the first failure occurs, transmitting a signal indicating the occurrence of the first failure to a process related to the execution of the application.

According to various embodiments, the method of allocating the virtual memory includes controlling not to transmit signals indicating occurrence of the other first failures to the process when other first failures of a specified number of times occur after the transmission of the signal. after the occurrence of the other first failures, if another first failure occurs, sending a signal indicating the occurrence of the another first failure to the process, and the number of the signals received by the process is When the specified value is exceeded, the method may further include determining whether to change the size of the heap area.

According to various embodiments, the failure of the memory allocation may include a second failure occurring when a storage space for the heap area among the areas included in the virtual memory is insufficient.

According to various embodiments, the setting of the information indicating the failure of the memory allocation includes, when the second failure occurs, including information for increasing the size of the heap area in the set information (eg, FIG. 5 ) of operation 550).

The electronic device according to various embodiments disclosed in this document may have various types of devices. The electronic device may include, for example, a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

The various embodiments of this document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, but it should be understood to include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more of the item, unless the relevant context clearly dictates otherwise. As used herein, "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "A , B, or C" each may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may simply be used to distinguish the component from other components in question, and may refer to components in other aspects (e.g., importance or order) is not limited. It is said that one (eg, first) component is "coupled" or "connected" to another (eg, second) component, with or without the terms "functionally" or "communicatively". When referenced, it means that one component can be connected to the other component directly (eg by wire), wirelessly, or through a third component.

The term “module” used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as, for example, logic, logic block, component, or circuit. can be used as A module may be an integrally formed part or a minimum unit or a part of the part that performs one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document include one or more stored in a storage medium (eg, internal memory 136 or external memory 138) readable by a machine (eg, electronic device 101). It may be implemented as software (eg, the program 140) including instructions. For example, a processor (eg, processor 120 ) of a device (eg, electronic device 101 ) may call at least one command among one or more commands stored from a storage medium and execute it. This makes it possible for the device to be operated to perform at least one function according to the called at least one command. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not include a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

According to an embodiment, the method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product is distributed in the form of a machine-readable storage medium (eg compact disc read only memory (CD-ROM)), or via an application store (eg Play Store ^TM ) or on two user devices ( It can be distributed (eg downloaded or uploaded) directly between smartphones (eg: smartphones) and online. In the case of online distribution, at least a part of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server.

According to various embodiments, each component (eg, module or program) of the above-described components may include a singular or a plurality of entities, and some of the plurality of entities may be separately disposed in other components. have. According to various embodiments, one or more components or operations among the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg, a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component are executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations are executed in a different order, or omitted. or one or more other operations may be added.

Claims (20)

In an electronic device,
memory for storing applications; and
a processor operatively coupled to the memory;
The processor is
If memory allocation for the virtual memory corresponding to the application fails during execution of the application, information indicating the failure of the memory allocation is set;
When the application is re-executed, if the set information exists, the size of the heap area included in the virtual memory is determined based on the set information,
The electronic device configured to allocate the virtual memory including the heap area of the determined size. The method according to claim 1,
The processor is
When the application is re-executed, if the set information exists, the electronic device is set to ignore a setting value of the size attribute of the heap area described in the setting file of the application. The method according to claim 1,
The processor is
Including the actual usage of the heap area according to the execution of the application in the set information,
The electronic device is configured to determine the size of the heap area based on the actual usage of the heap area. 4. The method according to claim 3,
The size of the heap area is set to a step value representing size ranges divided by a specified number,
The processor is
The electronic device for setting the size of the heap area as a step value indicating a size range in which the actual usage of the heap area is included among the size ranges. The method according to claim 1,
The failure of the memory allocation includes a first failure occurring when a storage space for a region other than the heap region among regions included in the virtual memory is insufficient. 6. The method of claim 5,
The processor is
The electronic device is configured to include information for reducing the size of the heap area in the set information when the first failure occurs. 6. The method of claim 5,
The processor is
When the first failure occurs, the electronic device is configured to transmit a signal indicating the occurrence of the first failure to a process related to the execution of the application. 8. The method of claim 7,
The processor is
after transmitting the signal, if a specified number of other first failures occur, controlling not to transmit signals indicating the occurrence of the other first failures to the process;
when another first failure occurs after the occurrence of the other first failures, sending a signal indicating the occurrence of the another first failure to the process;
The electronic device is configured to determine whether to change the size of the heap area when the number of signals received by the process exceeds a specified value. The method according to claim 1,
The failure of the memory allocation includes a second failure occurring when a storage space for the heap region among regions included in the virtual memory is insufficient. 10. The method of claim 9,
The processor is
The electronic device is configured to include information for increasing the size of the heap area in the set information when the second failure occurs. A method for allocating virtual memory in an electronic device, the method comprising:
setting information indicating failure of memory allocation when memory allocation to a virtual memory corresponding to the application fails during execution of an application stored in the memory of the electronic device;
determining a size of a heap area included in the virtual memory based on the set information if the set information exists when the application is re-executed; and
and allocating the virtual memory including the heap area of the determined size. 12. The method of claim 11,
The operation of determining the size of the heap area is
and ignoring a setting value of a size attribute of the heap area described in a setting file of the application when the set information exists. 12. The method of claim 11,
The operation of setting information indicating the failure of the memory allocation comprises:
including the actual usage of the heap area according to the execution of the application in the set information,
The operation of determining the size of the heap area is
and determining a size of the heap area based on the actual usage of the heap area. 14. The method of claim 13,
The size of the heap area is set to a step value representing size ranges divided by a specified number,
The operation of determining the size of the heap area is
and setting the size of the heap area to a step value indicating a size range in which the actual usage of the heap area is included among the size ranges. 12. The method of claim 11,
and the failure of the memory allocation includes a first failure occurring when a storage space for an area other than the heap area among areas included in the virtual memory is insufficient. 16. The method of claim 15,
The operation of setting information indicating the failure of the memory allocation comprises:
and including information for reducing the size of the heap area in the set information when the first failure occurs. 16. The method of claim 15,
and transmitting a signal indicating occurrence of the first failure to a process related to execution of the application when the first failure occurs. 18. The method of claim 17,
after transmitting the signal, when other first failures occur a specified number of times, controlling not to transmit signals indicating occurrence of the other first failures to the process;
when another first failure occurs after the occurrence of the other first failures, transmitting a signal indicating the occurrence of the another first failure to the process; and
and determining whether to change the size of the heap area when the number of signals received by the process exceeds a specified value. 12. The method of claim 11,
and the failure of the memory allocation includes a second failure occurring when a storage space for the heap area among the areas included in the virtual memory is insufficient. 20. The method of claim 19,
The operation of setting information indicating the failure of the memory allocation comprises:
and including information for increasing the size of the heap area in the set information when the second failure occurs.

Images