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

Abstract

In an electronic device, a memory for storing an application and a processor operatively connected to the memory, wherein the processor is configured to, if memory allocation for a virtual memory corresponding to the application fails during execution of the application, set information indicating a failure of the memory allocation, and, when the application is re-executed, if the set information exists, determine the size of a heap area included in the virtual memory based on the set information, and allocate the virtual memory including the heap area with the determined size. In addition to this, various embodiments are possible as identified through the present document.

Description

Method for allocating virtual memory and electronic device supporting the same {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 performs data processing or calculations may include a memory for storing data or instructions used by an application that is being executed. In order to more efficiently use the limited storage space of such memory, the electronic device may use virtual memory to provide more storage space than the capacity of the actual physically existing memory. For example, the electronic device may set a portion of the storage space of the memory as virtual memory, and control access to the storage space of the memory set as virtual memory to be performed through a virtual address (or logical address).

Meanwhile, 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 may include a stack area, which is a storage space for data that is temporarily stored, such as local variables used by an application, a heap area, which is a space dynamically allocated by an application, a data area, which is a space created when an application is executed, such as global variables or static variables used by an application, and returned to the system when the application is terminated, and a code area, which is a space where the application's instructions (or codes) are stored in the form of machine language.

The heap area of the virtual memory described above may include a native heap area and a Java virtual machine (JVM) heap area, where the JVM heap area may be determined by a setting value (e.g., "true" or "false" (default value)) of a size attribute of the heap area (e.g., an attribute defined as "largeHeap") described in a configuration file (e.g., the "AndroidManifest.xml" file) within the application package. For example, if the setting value of the size attribute of the heap area is set to "true", the JVM heap area may be allocated as the maximum available size (e.g., 1 GB).

Since existing electronic devices determine the size of the virtual memory heap area based on the setting value of the heap area size property described in the configuration file in the application package when the application is executed, the size of the heap area can be determined regardless of the actual usage. In addition, the size of the heap area is initialized once when the application is executed and can be difficult to adjust thereafter. Accordingly, when the virtual memory corresponding to the application is allocated, memory allocation may fail due to insufficient memory space.

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

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

In addition, a method for allocating virtual memory of an electronic device according to various embodiments of the present invention may include, when memory allocation for virtual memory corresponding to an application stored in a memory of the electronic device fails during execution of the application, an operation of setting information indicating a failure of the memory allocation; when the application is re-executed, if the set information exists, an operation of determining a size of a heap area included in the virtual memory based on the set information; and an operation of allocating the virtual memory including a heap area of the determined size.

According to various embodiments of the present invention, by determining the size of a heap area based on the actual usage of the heap area when allocating virtual memory corresponding to an application, the efficiency of storage space of virtual memory can be maximized.

In addition, according to various embodiments of the present invention, the stability of memory use can be increased by reducing the probability of failure in allocation of virtual memory.

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

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

Hereinafter, various embodiments of the present invention will be described with reference to the attached drawings. For convenience of explanation, components illustrated in the drawings may be exaggerated or reduced in size, and the present invention is not necessarily limited to what is illustrated.

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

The processor (120) may control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing, for example, software (e.g., a program (140)), and may perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculations, the processor (120) may store a command or data received from another component (e.g., a sensor module (176) or a communication module (190)) in the volatile memory (132), process the command or data stored in the volatile memory (132), and store result data in the nonvolatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphic processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a given function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

The auxiliary processor (123) may control at least a portion of functions or states associated with at least one of the components of the electronic device (101) (e.g., the display module (160), the sensor module (176), or the communication module (190)), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing device) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. Such learning may be performed, for example, in the electronic device (101) on which artificial intelligence is performed, or may be performed through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), deep Q-networks, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may additionally or alternatively include a software structure.

The memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto. The memory (130) can include volatile memory (132) or nonvolatile memory (134).

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

The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

The audio output module (155) can output an audio signal to the outside of the electronic device (101). The audio output module (155) can 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 can be used to receive an incoming call. According to one embodiment, the receiver can be implemented separately from the speaker or as a part thereof.

The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) can include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module (160) can include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can obtain sound through an input module (150), or output sound through an audio output module (155), or an external electronic device (e.g., an electronic device (102)) (e.g., a speaker or a headphone) directly or wirelessly connected to the electronic device (101).

The sensor module (176) can detect an operating state (e.g., power or temperature) of the electronic device (101) or an external environmental state (e.g., user state) and generate an electric signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) can 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, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). According to one 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) may be physically connected to an external electronic device (e.g., the electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

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

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

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

The battery (189) can power at least one component of the electronic device (101). In one embodiment, the battery (189) can include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

The communication module (190) may support establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., the electronic device (102), the electronic device (104), or the server (108)), and performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., the application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module or a power line communication module). Among these communication modules, a corresponding communication module may communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) may use subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196) to identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199).

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

The antenna module (197) can transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module (197) can include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) can include a plurality of antennas (e.g., 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), can be selected from the plurality of antennas by, for example, the communication module (190). A signal or power can be transmitted or received between the communication module (190) and the external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) can 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 may include a printed circuit board, an RFIC positioned on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) positioned on or adjacent a second side (e.g., a top side or a side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

At least some of the above components may be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)).

According to one embodiment, a command or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104 or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service by itself, request one or more external electronic devices to perform the function or at least part of the service. One or more external electronic devices that receive 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 the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a part of a response to the request. For this purpose, 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 by using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an IoT (Internet of Things) device. The server (108) may be an intelligent server using machine learning and/or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199). The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

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

Referring to FIG. 2, the electronic device (200) (e.g., the electronic device (101) of FIG. 1) may include a memory (210) (e.g., the memory (130) of FIG. 1) and a processor (230) (e.g., the processor (120) of FIG. 1). 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 components described above. For example, the electronic device (200) may further include at least one of the components illustrated in FIG. 1.

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

The processor (230) may control at least one other component of the electronic device (200) and perform various data processing or calculations. According to one 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) may use a virtual memory (250) to provide a larger storage space than the capacity of the memory (210) that actually physically exists, in order to more efficiently use the limited storage space of the memory (210). For example, the processor (230) may set a part of the storage space of the memory (210) as a virtual memory (250) and control access to the storage space of the memory (210) set as the virtual memory (250) to be performed through a virtual address (or a logical address).

The above 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 the processes of all applications (211). Here, a process may represent a program operating within a system, i.e., an electronic device (200). The user area may include a stack area (251), which 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), a data area (255), which is a space created when the application (211) is executed, such as global variables or static variables used by the application (211), and returned to the system when the application (211) is terminated, and a code area (257), which is a space where instructions (or codes) of the application (211) are stored in the form of machine language.

According to one embodiment, when executing an application (211), the processor (230) may determine the size of the heap area (253) of the virtual memory (250) corresponding to the application (211) according to the setting value (e.g., “true” or “false” (default value)) of the size attribute (e.g., an attribute defined as “largeHeap”) of the heap area (253) described in a configuration file of the application (211) (e.g., an “AndroidManifest.xml” file included in a package of the application (211). For example, when the setting value of the size attribute of the heap area (253) is set to “true,” the processor (230) may allocate a JVM heap area among the heap areas (253) to the maximum available size (e.g., 1 GB).

According to one embodiment, when executing an application (211), if there is information (hereinafter, referred to as a profile) indicating a failure in memory allocation for a virtual memory (250) corresponding to the application (211), the processor (230) may determine the size of the heap area (253) of the virtual memory (250) 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 a virtual memory (250) corresponding to the application (211) fails while executing the application (211), the processor (230) may set information indicating a failure in the memory allocation, i.e., a profile, and store the set profile in the memory (210). According to one embodiment, if the profile is not stored in the memory (210), the processor (230) can create a new profile, and if the profile is stored in the memory (210), the processor (230) can modify (or change) the stored profile. According to one embodiment, the profile can be stored in the memory (210) in the form of a file. In addition, if the profile exists, the processor (230) can 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 one embodiment, if 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, if the memory allocation fails, the processor (230) may check information about the actual usage of the heap area (253) based on the time at which the memory allocation failed and record it in the profile. In addition, 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 when allocating the virtual memory (250). Since 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) may be maximized, and the failure probability of memory allocation for the virtual memory (250) may be reduced.

According to one embodiment, the actual usage of the heap area (253) can be calculated based on the usage of the heap area (253) confirmed when a failure signal for memory allocation occurs due to lack of storage space of virtual memory (out of memory).

According to one embodiment, the size of the heap area (253) may be set as a step value representing size ranges divided by a specified number. For example, the size of the heap area (253) may be divided into a first step value (e.g., 256 MB), a second step value (e.g., 384 MB), and a third step value (e.g., 512 MB). The first step value may be a 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 a size range (e.g., 0 to 256 MB) less than or equal to the minimum value. 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 within a size range (e.g., 257 to 384 MB) less than or equal to the second step value, and the third step value may be set when the actual usage of the heap area (253) is greater than the second step value and is within a size range (e.g., 385 to 512 MB) less than or equal to the third step value. Here, the number of distinct step values is not limited thereto. The number of distinct step values may be determined according to the maximum available size of the heap area (253), and may be at least two or more.

According to one embodiment, the processor (230) may increase or decrease the size of the heap area (253) depending on the type of failure in memory allocation for the virtual memory (250). For example, if the failure in memory allocation is a first failure that occurs when there is a shortage of storage space for an area other than the heap area (253) among the areas included in the virtual memory (250), the processor (230) may reduce the size of the heap area (253). To this end, the processor (230) may include information for reducing the size of the heap area (253) in the profile. According to one embodiment, the processor (230) may record information for setting the size of the heap area (253) to a value at least one level lower in the profile. For example, if the current size of the heap area (253) is set to the third step value, the processor (230) can record information in the profile to set the size of the heap area (253) to the second step value or the first step value. For another example, if the current size of the heap area (253) is set to the second step value, the processor (230) can record information in the profile to set the size of the heap area (253) to the first step value.

As another example, if the failure of the memory allocation is a second failure that occurs when there is a shortage of storage space for the heap area (253) among the areas included in the virtual memory (250), the processor (230) may increase the size of the heap area (253). To this end, the processor (230) may include information for increasing the size of the heap area (253) in the profile. According to one embodiment, the processor (230) may record information in the profile to set the size of the heap area (253) to a value at least one level higher. For example, if the current size of the heap area (253) is set to the first level value, the processor (230) may record information in the profile to set the size of the heap area (253) to the second level value or the third level value. For another example, if the current size of the heap area (253) is set to the second step value, the processor (230) may record information in the profile to set the size of the heap area (253) to the third step value.

The first failure may indicate a failure due to, for example, a lack of storage space (e.g., "ENOMEM (out of memory)"), which occurs when using a function that performs a memory mapping function for a file (e.g., the mmap() function). The second failure may indicate a failure due to, for example, a lack of storage space in a JVM heap area (e.g., "JVM OOM (out of memory)").

According to one embodiment, 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) when the first failure occurs. If the actual usage of the heap area (253) is less than a step value for reducing the size of the heap area (253) when the first failure occurs, the processor (230) may set the size of the heap area (253) to 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 size of the heap area (253) when the first failure occurs may be set to the second step value. For another 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 first step value, the size of the heap area (253) according to the occurrence of the first failure can be set to the second step value or the first step value.

According to one embodiment, the processor (230) may not change the size of the heap area (253) when both the occurrence history of the first failure and the occurrence history of the second failure exist while the size of the heap area (253) is the same. For example, when the size of the heap area (253) is set to the second step value and the first failure and the second failure occur, the processor (230) may maintain the size of the heap area (253).

According to one embodiment, when the sizes of the heap areas (253) are not the same, and both a history of the first failure and a history of the second failure exist, 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). When a settable size exists between the size of the heap area (253) at the time when the first failure occurred and the size of the heap area (253) at the time when the second failure occurred, the processor (230) may determine 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) may be set to the settable size. For example, if the second failure occurs when the size of the heap area (253) is the first step value, and if the first failure occurs when the size of the heap area (253) is the third step, the processor (230) can check whether the actual usage of the heap area (253) is a value between the first step value and the third step value that is smaller than the second step value, and if the actual usage of the heap area (253) is smaller than the second step value, the size of the heap area (253) can be set to the second step value. For another example, if the second failure occurred when the size of the heap area (253) is the first step value, and the first failure occurred when the size of the heap area (253) is the second step, since there is no step value that can be set between the first step value and the second step value, the processor (230) can set the size of the heap area (253) to the second step value by considering the actual usage of the heap area (253).

In the above description, the case where the size of the heap area (253) is set to a step value representing a size range divided by a specified number has been described, but it is not limited thereto. According to various embodiments, the processor (230) may set the size of the heap area (253) to a value that is larger than the actual usage of the heap area (253) by a specified size or more. In this case, the processor (230) may set the size of the heap area (253) to a size corresponding to the unit processing amount (e.g., page size) of the memory (210).

According to one embodiment, the size of the heap area (253) may be a memory size value (e.g., 0 to 1 GB) calculated based on actual usage. For example, the size of the heap area (253) may be a size calculated by adding a margin value (e.g., 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 the actual usage.

According to one embodiment, if the failure of the memory allocation is a first failure that occurs when there is insufficient storage space for an area other than the heap area (253) among the areas included in the virtual memory (250), the processor (230) may record information in the profile to set the size of the heap area (253) to a value smaller by a specified or calculated size. For example, if the current size of the heap area (253) is set to a first set value, the processor (230) may record information in the profile to set the size of the heap area (253) to a second set value smaller than the first set value.

According to one embodiment, if the failure of the memory allocation is a second failure that occurs when there is insufficient storage space for the heap area (253) among the areas included in the virtual memory (250), the processor (230) may record information in the profile to set the size of the heap area (253) to a value that is larger than the specified or calculated size. For example, if the current size of the heap area (253) is set to a first set value, the processor (230) may record information in the profile to set the size of the heap area (253) to a second set value that is larger than the first set value.

According to one 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 one embodiment, the signal may include a result value (e.g., a result value of failure or success) of an independently executable SW module among the internal operations 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 (the first failure) may occur multiple times after it occurs once, the processor (230) may control, after transmitting the signal, so that if a specified number of (e.g., 50) other first failures of the same type occur, signals indicating the occurrence of the other first failures are not transmitted to the process. In addition, if another first failure occurs after the specified number of other first failures occur, the processor (230) may transmit a signal indicating the occurrence of the newly occurred other first failure to the process. In one embodiment, the processor (230) may include information about 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 one embodiment, the processor (230) may determine whether to change the size of the heap area (253) if the number of signals indicating the occurrence of the first failure included in the profile exceeds a specified value (e.g., 3 times). For example, 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) and the occurrence history of the second failure if the number of signals indicating the occurrence of the first failure exceeds the specified value.

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

As described above, according to various embodiments, an electronic device (e.g., the electronic device (200) of FIG. 2) may include a memory (e.g., the memory (210) of FIG. 2) that stores an application (e.g., the application (211) of FIG. 2), and a processor (e.g., the processor (230) of FIG. 2) operatively connected to the memory, wherein the processor may be configured to, when memory allocation for a virtual memory (e.g., the virtual memory (250) of FIG. 2) corresponding to the application fails during execution of the application, set information indicating a failure of the memory allocation, and, when the application is re-executed, if the set information exists, determine the size of a heap area (e.g., the heap area (253) of FIG. 2) included in the virtual memory based on the set information, and allocate the virtual memory including the heap area having the determined size.

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

According to various embodiments, the processor may be configured to include actual usage of the heap area according to execution of the application in the set information, and determine 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 representing a size range divided by a specified number, and the processor can set the size of the heap area to a step value representing a size range within which an actual usage of the heap area is included among the size ranges.

According to various embodiments, the failure of the memory allocation may include a first failure that occurs when there is insufficient storage space for an area other than the heap area among the areas included in the virtual memory.

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

According to various embodiments, the processor may be configured to, upon occurrence of the first failure, transmit a signal indicating occurrence of the first failure to a process associated with execution of the application.

According to various embodiments, the processor may be configured to control not to transmit signals indicating occurrence of other first failures to the process if a specified number of other first failures occur after the transmission of the signal, to transmit a signal indicating occurrence of other first failures to the process if another first failure occurs after the occurrence of the other first failures, and to determine whether to change the size of the heap area if the number of the signals received by the process exceeds a specified value.

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

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

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

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

If it is determined that the memory allocation for the virtual memory has failed, the processor may set information (hereinafter, referred to as a profile) indicating the failure of the memory allocation for the virtual memory at operation 330. In addition, the processor may store the set profile in a memory (e.g., the memory (210) of FIG. 2). According to one embodiment, if 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 may modify (or change) the stored profile. According to one embodiment, the profile may be stored in the memory in the form of a file.

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

According to one embodiment, if the memory allocation fails, the processor may include the actual usage of the heap area according to the execution of an application (e.g., 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 one embodiment, if the failure of the memory allocation is a first failure that occurs when there is insufficient storage space for an area other than the heap area among the areas included in the virtual memory, the processor may include information for reducing the size of the heap area in the profile. For example, the processor may record information for setting the size of the heap area to a value at least one level lower in the profile. In this case, the processor may set the information regarding whether the size of the heap area included in the profile is changed to a value indicating a size reduction.

According to one embodiment, if the failure of the memory allocation is a second failure that occurs when there is insufficient storage space for the heap area among the areas included in the virtual memory, the processor may include information for increasing the size of the heap area in the profile. For example, the processor may record information for setting the size of the heap area to a value at least one level higher in the profile. In this case, the processor may set the information regarding whether the size of the heap area included in the profile is changed to a value indicating a size increase.

According to one embodiment, 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 when the first failure occurs. For example, if the actual usage of the heap area is less than a step value for reducing the size of the heap area when the first failure occurs, the processor may set the size of the heap area to the step value. In this case, the processor may set the information on whether to change the size of the heap area included in the profile to a value indicating a size reduction.

According to one embodiment, when the size of the heap area is the same and both the occurrence history of the first failure and the occurrence history of the second failure exist, the processor may set the change value of the size of the heap area included in the profile to zero or delete it. For example, when the size of the heap area is the same and both the first failure and the second failure occur, the processor may set the information on whether the size of the heap area included in the profile has been changed to a value indicating size maintenance.

According to one embodiment, when the sizes of the heap areas are not the same, and both a history of the first failure and a history of the second failure exist, the processor may set information on whether the size of the heap area has changed based on the actual usage of the heap area. For example, when a configurable size exists between the size of the heap area at the time when the first failure occurred and the size of the heap area at the time when the second failure occurred, the processor may determine whether the actual usage of the heap area is smaller than the configurable size, and if the actual usage of the heap area is smaller than the configurable size, the processor may set the size of the heap area to the configurable size. In this case, the processor may set the information on whether the size of the heap area included in the profile has changed to a value indicating a size increase. For another example, if there is no settable size between the size of the heap area at the time when the first failure occurred and the size of the heap area at the time when the second failure occurred, the processor may set the size of the heap area to a value larger than the size of the existing heap area, taking into account the actual usage of the heap area. In this case as well, the processor may set the information on whether the size of the heap area included in the profile has been changed to a value indicating a size increase.

According to one 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, if a specified number of other first failures of the same type occur, the processor may control signals indicating the occurrence of the other first failures not to be transmitted to the process. In addition, when another first failure occurs after the specified number of other first failures occur, the processor may transmit a signal indicating the occurrence of the newly occurred other first failure to the process. At this time, the processor may include information about 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 the occurrence of the first failure included in the profile exceeds a specified value, the processor may set information about whether to change the size of the heap area included in the profile to a value indicating a size reduction.

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

FIG. 4 is a drawing for explaining a method for allocating virtual memory according to one embodiment of the present invention.

Referring to FIG. 4, a processor (e.g., a processor (230) of FIG. 2) of an electronic device (e.g., an electronic device (200) of FIG. 2) may determine, at operation 410, whether there is information (hereinafter, referred to as a profile) indicating a failure in memory allocation for a virtual memory (e.g., a virtual memory (250) of FIG. 2). For example, the processor may determine, when executing an application (e.g., an application (211) of FIG. 2) stored in a memory (e.g., a memory (210) of FIG. 2), whether there is a profile stored in the memory.

If it is determined that the above profile does not exist, the processor may determine the size of a heap area (e.g., the heap area (253) of FIG. 2) based on a configuration file of the application (e.g., an "AndroidManifest.xml" file included in a package of the application) at operation 430. For example, the processor may determine the size of a heap area of a virtual memory corresponding to the application based on a setting value (e.g., "true" or "false" (default value)) of a size attribute of the heap area (e.g., an attribute defined as "largeHeap") described in the configuration file of the application. For example, if the setting value of the size attribute of the heap area is set to "true", the processor may allocate a JVM heap area among the heap areas to a maximum available size (e.g., 1 GB).

If it is determined that the profile exists, the processor may determine the size of the heap area based on the profile at operation 450. According to one 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 to be a value that is larger than a specified size or more than the actual usage of the heap area. According to one embodiment, the processor may determine the size of the heap area based on a size change value of the heap area included in the profile. For example, the processor may determine the size of the heap area as the size change value of the heap area. Here, the size change value of the heap area may include a value set to a value that is larger than a specified size or more than the actual usage of the heap area, or one of step values (e.g., a first step value, a second step value, or a third step value) representing size ranges in which the size of the heap area is divided into a specified number of step values.

According to one embodiment, the processor can maintain the size of the heap area if the information regarding whether the size of the heap area included in the profile is set to a value indicating size maintenance. According to another embodiment, the processor can decrease the size of the heap area by a size change value of the heap area included in the profile if the information regarding whether the size of the heap area included in the profile is set to a value indicating size decrease. According to yet another embodiment, the processor can increase the size of the heap area by a size change value of the heap area included in the profile if the information regarding whether the size of the heap area included in the profile is set to a value indicating size increase.

Once the size of the heap area is determined, the processor can set (or allocate) the virtual memory including the heap area of the determined size at operation 470.

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

Referring to FIG. 5, a processor (e.g., a processor (230) of FIG. 2) of an electronic device (e.g., an electronic device (200) of FIG. 2) may increase or decrease a size of a heap area (e.g., a heap area (253) of FIG. 2) included in a virtual memory (e.g., a virtual memory (250) of FIG. 2)) depending on a type of failure in memory allocation for the virtual memory. The failure in memory allocation for the virtual memory may include, for example, a first failure due to insufficient storage space that occurs when a function that performs a memory mapping function for a file is used, and a second failure due to insufficient storage space of a JVM heap area. The first failure may occur when there is insufficient storage space for an area other than the heap area among areas included in the virtual memory, and the second failure may occur when there is insufficient storage space for the heap area among areas included in the virtual memory.

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

If it is determined that the failure of the above memory allocation is not a failure due to insufficient storage space for the heap area, that is, if the failure of the memory allocation is a failure due to insufficient storage space for an area other than the heap area (the first failure), the processor may, in operation 530, set information (hereinafter, referred to as a “profile”) indicating a failure of the memory allocation for the virtual memory to include information for reducing the size of the heap area. For example, the processor may set information regarding whether the size of the heap area included in the profile has changed to a value indicating a size reduction. In addition, the processor may set a size change value of the heap area included in the profile to a value smaller than the current size of the heap area, or to a step value at least one step lower than a step value set to the current size of the heap area.

If it is determined that the failure of the above memory allocation is a failure due to a lack of storage space for the heap area, that is, if the failure of the above memory allocation is a failure due to a lack of storage space for the heap area (the second failure), the processor may set the profile to include information for increasing the size of the heap area at operation 550. For example, the processor may set the information regarding whether the size of the heap area, included in the profile, has changed to a value indicating a size increase. In addition, the processor may set 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 to a step value at least one step higher than the step value set to the current size of the heap area.

Although the processor in the above-described operation 510 has been described as determining whether the failure of the memory allocation is a failure due to a lack of storage space for the heap area (the second failure), it is not limited thereto. In some embodiments, the processor in the operation 510 may determine whether the failure of the memory allocation is a failure due to a lack of storage space for an area other than the heap area (the first failure). In this case as well, if the processor determines that the failure of the memory allocation is a failure due to a lack of storage space for an area other than the heap area, the processor may perform operation 530, and if the processor determines that the failure of the memory allocation is not a failure due to a lack of storage space for an area other than the heap area, the processor may perform operation 550.

When the profile is set to include information for decreasing 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 (e.g., the memory (210) of FIG. 2). According to one embodiment, the processor may store the profile in the memory in the form of a file.

FIG. 6 is a diagram for explaining processing operations related to allocation of virtual memory according to one embodiment of the present invention.

Referring to FIG. 6, an electronic device (e.g., the electronic device (200) of FIG. 2) may include an application (610) (e.g., the application (211) of FIG. 2), a virtual machine (630), and a heap area setting module (650). The virtual machine (630) (e.g., a Java virtual machine (JVM)) is a program executed by a processor (e.g., the processor (230) of FIG. 2) of the electronic device, and may provide an installation and execution environment for an operating system or an application program (e.g., the application (610)). The virtual machine (630) may include a virtual memory setting module (631) that allocates virtual memory (e.g., virtual memory (250) of FIG. 2) corresponding to the application (610), a memory allocation failure detection module (633) that detects a failure in memory allocation for the virtual memory, a signal processing module (635) that processes a signal indicating the occurrence of a failure in the memory allocation, and a profile setting module (637) that sets information (hereinafter, referred to as a profile (651)) indicating a failure in memory allocation for the virtual memory. The heap area setting module (650) may determine the size of a heap area (e.g., a heap area (253) of FIG. 2) of a virtual memory corresponding to the application (610).

When an execution request for the application (610) occurs, the virtual machine (630) can execute the application (610) at operation 671. During the execution process of the application (610), the virtual memory configuration module (631) of the virtual machine (630) can allocate virtual memory corresponding to the application (610) at operation 672. According to one embodiment, the virtual memory configuration module (631) can determine the size of the heap area of the virtual memory based on the configuration file (611) of the application (610) (e.g., the "AndroidManifest.xml" file included in the package of the application (610). For example, the virtual memory configuration module (631) can determine the size of the heap area of the virtual memory based on the configuration value (e.g., "true" or "false" (default value)) of the size attribute of the heap area described in the configuration file (611) (e.g., the attribute defined as "largeHeap").

During execution of the application (610), if a failure (first failure) occurs due to insufficient storage space for an area other than the heap area among the areas included in the virtual memory, the memory allocation failure detection module (633) of the virtual machine (630) may detect the failure at operation 673. Detecting the failure may mean detecting a system event that occurs when memory allocation fails due to insufficient storage space. In addition, the memory allocation failure detection module (633) may transmit a signal of failure of memory allocation due to insufficient storage space (a signal indicating occurrence of the first failure) to the signal processing module (635) of the virtual machine (630) at operation 674. According to one embodiment, the memory allocation failure detection module (633) may not transmit failure signals indicating occurrence of other failures to the signal processing module (635) if a specified number of (e.g., 50) other failures of the same type are detected after transmitting the failure signal. In addition, the memory allocation failure detection module (633) may transmit a failure signal indicating occurrence of a newly detected failure to the signal processing module (635) if another failure of the same type (the first failure) is detected after detecting the specified number of other failures of the same type. The signal processing module (635) that receives the failure signal may execute the profile setting module (637) in operation 674-1.

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

If the number of receptions of the above failure signal exceeds a specified value (e.g., 3 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 the size of the heap area included in the profile (651) has changed to a value indicating a size reduction.

If a failure (second failure) occurs due to insufficient storage space for the heap area among the areas included in the virtual memory, the profile setting module (637) can record the number of occurrences of failure due to insufficient storage space for the heap area in the profile (651) in operation 675-2. In addition, the profile setting module (637) can set information on whether the size of the heap area included in the profile (651) has changed to a value indicating a size increase. In addition, the profile setting module (637) can record the actual usage of the heap area in the profile (651).

According to one embodiment, if the number of receptions of the failure signal exceeds the specified value, the profile setting module (637) can check the number of occurrences of failures due to insufficient storage space for the heap area. Considering the number of occurrences of failures due to insufficient storage space for the heap area, the profile setting module (637) can determine whether to change the size of the heap area. If a change in the size of the heap area is determined, the profile setting module (637) can set information on whether to change the size of the heap area in the profile (651). In addition, the profile setting module (637) can set a size change value of the heap area in the profile (651).

When a request for re-execution of the application (610) occurs, the virtual machine (630) can re-execute the application (610) at operation 676. During the re-execution process of the application (610), the virtual memory setting module (631) allocates virtual memory corresponding to the application (610). At this time, if the profile (651) exists (if the profile (651) is stored), the heap area setting module (650) can determine the size of the heap area of the virtual memory based on the profile (651) at operation 677. For example, the heap area setting module (650) can set (or change) the size of the heap area based on the 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) can be ignored. According to one 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) can reset the information recorded in the profile (651). In some embodiments, the heap area setting module (650) can reset the remaining information except for the size change value of the heap area recorded in the profile (651).

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

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

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

According to various embodiments, the operation of setting information indicating a failure of the memory allocation may include an operation of including an actual usage of the heap area according to execution of the application in the set information, and the operation of determining the size of the heap area may include an operation of 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 representing a size range divided by a specified number, and the operation of determining the size of the heap area may include an operation of setting the size of the heap area to a step value representing a size range within which an actual usage amount of the heap area is included among the size ranges.

According to various embodiments, the failure of the memory allocation may include a first failure that occurs when there is insufficient storage space for an area other than the heap area among the areas included in the virtual memory.

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

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

According to various embodiments, the method for allocating virtual memory may further include: an operation for controlling, if a specified number of other first failures occur after transmitting the signal, not to transmit signals indicating occurrence of the other first failures to the process; an operation for transmitting, if another first failure occurs after the occurrence of the other first failures, a signal indicating occurrence of the other first failure to the process; and an operation for determining, if the number of the signals received by the process exceeds a specified value, whether to change the size of the heap area.

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

According to various embodiments, the operation of setting information indicating a failure of the memory allocation may include an operation of including information for increasing the size of the heap area in the set information when the second failure occurs (e.g., operation 550 of FIG. 5).

The electronic devices according to various embodiments disclosed in this document may be devices of various forms. The electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliance devices. The electronic devices according to embodiments of this document are not limited to the above-described devices.

It should be understood that the various embodiments of this document and the terminology used herein are not intended to limit the technical features described in this document to specific embodiments, but include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly dictates otherwise. In this document, each of the phrases "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 "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), 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 may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally configured component or a minimum unit of the component or a portion thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store ^TM ) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium, such as a memory of a manufacturer's server, a server of an application store, or an intermediary server.

According to various embodiments, each component (e.g., a module or a program) of the above-described components may include a single or multiple entities, and some of the multiple entities may be separately arranged in other components. According to various embodiments, one or more components or operations of the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, the multiple components (e.g., a module or a program) may be integrated into one component. In such a case, the integrated component may perform one or more functions of each of the multiple components identically or similarly to those performed by the corresponding component of the multiple components before the integration. According to various embodiments, the operations performed by the module, program, or other component may be executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims (20)

In electronic devices,
Memory for storing commands and applications; and
comprising at least one processor comprising processing circuitry;
The above instructions are collectively or individually executed by the at least one processor, such that the electronic device:
If memory allocation of the virtual memory for the application fails due to insufficient storage space for at least one area among a plurality of areas included in the virtual memory corresponding to the application during execution of the application, information indicating the failure of the memory allocation is set, and the set information includes information for setting the size of an area to be occupied by a heap area among a plurality of areas included in the virtual memory,
When the above application is re-executed, if the above set information exists, the size value of the area to be occupied by the heap area among the multiple areas included in the virtual memory is determined based on the above set information,
If the determined size value is different from the size value of the heap area in the virtual memory when the memory allocation fails, the size of the area occupied by the heap area in the virtual memory is changed to the determined size value,
An electronic device set to allocate the virtual memory including the heap area changed to the determined size value for the re-executed application.
In claim 1,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
An electronic device configured to ignore the setting value of the size attribute of the heap area described in the configuration file of the application when the above-described application is re-executed, if the above-described set information exists.
In claim 1,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
The actual usage of the heap area according to the execution of the above application is included in the above set information,
An electronic device configured to determine the size of said heap area based on actual usage of said heap area.
In claim 3,
The size of the above heap area is set to a step value representing a size range divided by a specified number,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
An electronic device that sets the size of the heap area to a step value representing a size range within which the actual usage of the heap area is included among the above size ranges.
In claim 1,
An electronic device in which the above memory allocation failure includes a first failure that occurs when there is insufficient storage space for an area other than the heap area among the areas included in the virtual memory. In claim 5,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
An electronic device configured to include information for reducing the size of the heap area in the set information when the first failure occurs.
In claim 5,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
An electronic device configured to transmit a signal indicating the occurrence of the first failure to a process associated with the execution of the application when the first failure occurs.
In claim 7,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
After the transmission of the above signal, if a specified number of other first failures occur, control is provided so that signals indicating the occurrence of the other first failures are not transmitted to the process.
After the occurrence of the above other first failures, if another first failure occurs, a signal indicating the occurrence of the above other first failure is transmitted to the process,
An electronic device configured to determine whether to change the size of the heap area if the number of said signals received by said process exceeds a specified value.
In claim 1,
The failure of the above memory allocation includes a second failure that occurs when there is insufficient storage space for the heap area among the areas included in the virtual memory,
The above instructions are collectively or individually executed by the at least one processor, so that the electronic device,
An electronic device configured to include information for increasing the size of the heap area in the set information when the second failure occurs.
delete In a method of allocating virtual memory of an electronic device,
An operation of setting information indicating a failure of the memory allocation when memory allocation of the virtual memory for the application fails due to insufficient storage space for at least one area among a plurality of areas included in a virtual memory corresponding to the application while the application stored in the memory of the electronic device is being executed, the set information including information for setting a size of an area to be occupied by a heap area among a plurality of areas included in the virtual memory;
When the application is re-executed, if the set information exists, an operation of determining the size value of an area to be occupied by the heap area among the multiple areas included in the virtual memory based on the set information;
If the determined size value is different from the size value of the heap area in the virtual memory when the memory allocation fails, an operation of changing the size of the area occupied by the heap area in the virtual memory to the determined size value; and
A method for allocating virtual memory, comprising an operation of allocating the virtual memory including the heap area changed to the determined size value for the re-executed application. delete delete delete delete delete delete delete delete delete