CN114020652B - Application program management method and electronic equipment - Google Patents

Abstract

The embodiment of the application provides a management method of an application program, which comprises the following steps: monitoring the application result of the graphic buffer area in the running process of the application program; if the application result of the image buffer area is application failure, analyzing the failure type according to the application result; if the failure type is memory mapping failure, acquiring the virtual memory occupation condition of the application program; if the virtual memory occupied by the application program exceeds a preset threshold value, starting a suicide recovery function of the application program to release the memory occupied by the application program, avoiding serious consequences such as system crash, deadlocking and the like caused by memory leakage, and reducing the influence on the use of a user.

Description

Application program management method and electronic device

technical field

The present application relates to the field of electronics, and in particular to an application program management method and electronic equipment.

Background technique

Memory leak refers to the phenomenon that the dynamically allocated heap memory in the application is not released or cannot be released in time for some reason, resulting in the waste of system memory.

However, since memory leaks are not fault-type errors, there are currently problems that are difficult to detect and locate, which will eventually lead to serious consequences such as memory overflow, abnormal operation of applications, and even system freezes.

Contents of the invention

This application provides a method for managing application programs, which can avoid the current system stuck situation caused by memory leaks.

In the first aspect, an application management method is provided, including: monitoring the application result of the graphics buffer during the running of the application; if the application result of the image buffer is application failure, analyzing the failure type according to the application result; If the failure type is memory mapping failure, the virtual memory occupation of the application is obtained; if the virtual memory occupied by the application exceeds a preset threshold, the suicide recovery function of the application is started.

During the running of the application, in order to draw the interface and save the drawn data, the running process will apply for a graphics buffer (graphicbuffer) from the system memory.

Exemplarily, a graphics buffer shared between processes may be applied for through graphicbuffermapper, and a graphics buffer used by an application may also be applied for through a graphicbufferallocator process interface.

Since there may be a memory leak when applying for a graphics buffer from the memory manager, when the application process initiates a graphics buffer application, the memory application monitoring function can be enabled to monitor the application result of the graphics buffer.

It should be noted that the memory application monitoring function can also be enabled when the application starts running, and the virtual memory usage of the application can be obtained in real time. When the virtual memory usage of the application exceeds a certain value (this value can be determined according to It can be set according to the actual application scenario, which is not limited in this application), and the memory application monitoring function can be enabled. It can also be activated when the virtual memory occupation of the application exceeds a certain value and the process of the application initiates a graphics buffer application. Memory application monitoring function, of course, the memory application monitoring function can also be activated in other situations.

Exemplarily, the above-mentioned enabling of the memory application monitoring may include: a manner in which the user actively enables the memory application monitoring function, a manner in which the electronic device automatically enables the memory application monitoring function, and a manner in which the memory application monitoring function is enabled by default.

The application result of the above graphics buffer application includes application success and application failure.

When the available memory of the system satisfies the application, and the applied memory can be mapped to the address of the virtual memory of the process, the memory manager will return the result of the successful application.

When the available memory of the system is too small (the memory occupied by the requested graphics buffer is larger than the available memory of the system), the requested memory cannot be mapped to the address of the virtual memory of the process, or other abnormal conditions, the memory manager will return the result of the application failure .

Among them, the virtual memory usage of the application can be called out through the /proc/self/status function.

Wherein, the preset threshold can be set according to the application program, for example, for a 32-bit application program, the above preset threshold can be set to 3.7G. Of course, for 32-bit applications, the above preset threshold can be set to some value lower than 3.7G, such as 3.5G, 3.2G and so on.

It can be seen from the above that by monitoring the process of the application program to apply for a graphics buffer to the system memory, when the memory application fails due to excessive use of virtual memory, the suicide recovery function is activated to release the memory occupied by the application program. Memory, to avoid serious consequences such as system crashes and freezes caused by memory leaks, and reduce the impact on users.

In a possible implementation manner of the first aspect, if the virtual memory occupied by the application exceeds the preset threshold, starting the suicide recovery function includes: ending the application when the virtual memory occupied by the application exceeds the preset threshold All processes of the program.

When the virtual memory occupied by the application program exceeds the preset threshold, a command to end all processes of the application program can be sent to the process manager. In response to the command, the process manager will end all processes of the application program and release the System memory used by this application.

The process manager contains all the processes currently running in the system, and the system memory occupied by the application can be released by ending all the processes related to the application name through the process manager.

The above-mentioned automatic scanning and killing of the application program can directly end all processes of the application program. At this time, the display interface of the electronic device will directly jump to display the main screen interface of the electronic device, that is, the user feels that the application program has flashed back. Directly ending all processes of the application program can release all the memory occupied by the application program, avoiding serious consequences such as system crashes and freezing caused by memory leaks.

In a possible implementation of the first aspect, if the above-mentioned virtual memory occupied by the application exceeds the preset threshold, the suicide recovery function is activated, including: when the virtual memory occupied by the application exceeds the preset threshold, judging the Whether the process of the graphics buffer is the main process of the application program;

If the process applying for the graphics buffer is the main process of the application program, then restart the main process of the application program after ending all the processes of the application program; otherwise, end all the processes of the application program.

If the process applying for the graphics buffer is the main process of the application, then the interface displayed by the electronic device is the main display interface of the application. The main process, at this time, the display interface of the electronic device will directly jump to the main display interface of the application program.

Since the time interval between launching the main process of the application program after the process of the application program is terminated is very short, the user is not aware of this, and can only feel that the display interface of the electronic device jumps back to the main display interface of the application program. At this time, the user will not experience the crash of the application program, so the system memory occupied by the application program can be released while the impact on the user's use can be avoided, and the user experience can be improved.

In a possible implementation manner of the first aspect, after monitoring the application result of the graphics buffer during the running of the application program, it further includes:

If the application result of the graphics buffer application is that the application is successful, the applied memory is mapped to the address of the virtual memory of the process.

After the graphics buffer application is successful (that is, the system allocates memory to the process), the graphics buffer needs to be mapped to the address space of the virtual memory corresponding to the process, so that the process can display and draw the interface.

In a possible implementation manner of the first aspect, the above application management method further includes: if the failure type is not a memory mapping failure, outputting an exception log corresponding to the failure type.

The failure types when the above application fails may include too little available memory in the system, memory mapping failure, other abnormal conditions, etc., which are not limited here.

In some embodiments, the electronic device may determine the failure type according to the application result returned by the memory manager. For example, the type of failure can be determined by analyzing the code corresponding to the 2 of the application result.

Exemplarily, when the application result includes two fields, the first field is used to indicate whether the application is successful, and the second field is used for the type of failure, indicating that the code of the second field is read and based on the code of the second field The memory application result can be determined.

For example, if the application result is "01,001", read the content "001" in the second field, and according to the predetermined meaning corresponding to the code, it can be known that the failure type is too little available memory in the system. For another example, if the application result is "01,010", the read content of the second field is "010". According to the meaning corresponding to the predetermined code, the failure type is a memory mapping failure.

As another example, when the application result only contains one field, where the 2nd to 4th digits of the field are used to indicate the type of failure, then read the codes of the 2nd to 4th digits, based on the second to 4th digits The encoding of the bit determines the application result of the memory application.

For example, if the application result is "1001", read the code "001" from the second to the fourth digit, and according to the predetermined meaning corresponding to the code, it can be known that the failure type is too little available memory in the system. For another example, if the application result is "1010", read the code "010" from the 2nd to 4th digits. According to the predetermined meaning corresponding to the code, it can be known that the failure type is memory mapping failure.

For another example, when the application result is returned as an error with an error code, the failure type can be determined through the error code.

Since the failure type is not a memory mapping failure, it will basically not cause a memory leak, so there is no need to perform any operations on the application, and only need to output the exception log corresponding to the failure type.

In some embodiments, the above-mentioned exception log may include the name of the process initiated by the application, the time when the exception occurred, and the content of the exception. The content of the exception includes the failure to apply for the graphics buffer and the type of failure. Exemplarily, when the failure type is too little available memory in the system, the above abnormal content may be that process B of application A fails to apply for a graphics buffer at time xx due to too little system memory.

In some embodiments, when the failure type is too little system memory, based on the exception log, the electronic device can start the LMK mechanism.

In some embodiments, the above exception log may be stored in a log manager, and the electronic device may read the exception log through the log manager.

In a possible implementation manner of the first aspect, the above application management method further includes: if the virtual memory occupied by the application does not exceed a preset threshold, outputting an exception log indicating that memory mapping fails and the virtual memory does not exceed the threshold.

Since the virtual memory occupied by the application does not exceed the preset threshold, that is, it will not cause a memory leak, so there is no need to perform any operations on the application, only the exception log that the memory mapping fails and the virtual memory does not exceed the threshold needs to be output.

In a possible implementation manner of the first aspect, the above-mentioned application management method further includes: after ending all processes of the application, outputting an exception indicating that the operation of the application is terminated because the virtual memory usage is too high log.

The abnormal situation of ending the operation of the application program due to excessive virtual memory usage is recorded in the form of an exception log, which is convenient for the user to view.

In a second aspect, an embodiment of the present application provides an electronic device, including:

The monitoring module is used to monitor the application result of the graphics buffer during the running of the application program;

The analysis module is used to analyze the failure type according to the application result if the application result of the image buffer is application failure;

The obtaining module is used to obtain the virtual memory usage of the application if the failure type is a memory mapping failure;

The suicide recovery module is configured to start the suicide recovery function of the application program if the virtual memory occupied by the application program exceeds a preset threshold.

In the third aspect, the embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and operable on the processor. When the processor executes the computer program, any one of the above-mentioned first aspects can be realized. Methods.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method according to any one of the above-mentioned first aspects is implemented.

In the fifth aspect, the embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled with the memory, and the processor executes the computer program stored in the memory, so as to realize the above-mentioned any one of the first aspect. method. The chip system can be a single chip, or a chip module composed of multiple chips.

In a sixth aspect, an embodiment of the present application provides a computer program product, which, when the computer program product is run on an electronic device, causes the electronic device to execute the method described in any one of the above-mentioned first aspects.

It can be understood that, for the beneficial effects of the above-mentioned second aspect to the sixth aspect, reference can be made to the related description in the above-mentioned first aspect, which will not be repeated here.

Description of drawings

FIG. 1 is an exemplary schematic diagram of an abnormal display of an application program caused by a memory leak provided by an embodiment of the present application.

FIG. 2 is a schematic diagram of a hardware structure of a mobile phone provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of a software system architecture of a mobile phone provided by an embodiment of the present application.

Fig. 4 is a schematic diagram of a graphical user interface in some application scenarios provided by an embodiment of the present application.

FIG. 5 is a schematic diagram of some graphical user interfaces during the process of enabling the memory application monitoring function provided by the embodiment of the present application.

FIG. 6 is a schematic diagram of an implementation flow of an application program management method provided by an embodiment of the present application.

FIG. 7 is a schematic diagram of an implementation flow of another application program management method provided by the embodiment of the present application.

detailed description

It should be noted that the terms used in the implementation manners of the embodiments of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. In the description of the embodiments of the present application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this article is only a description of associations A relationship means that there may be three kinds of relationships, for example, A and/or B means: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more than two, "at least one", "one or more" means one, two or two above.

Hereinafter, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features. Thus, the definition of "first" and "second" features may expressly or implicitly include one or more of these features.

Reference to "one embodiment" or "some embodiments" or the like in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean "one or more but not all embodiments" unless specifically stated otherwise. The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless specifically stated otherwise.

In order to better understand the embodiments of the present application, terms or concepts that may be involved in the embodiments are introduced below.

1. Graphics buffer (graphicbuffer)

It is used for display drawing of the interface of the application program and saves display drawing data. When the application is running, it needs to first apply for the graphics buffer for displaying the interface and saving the displaying data. The specific graphics buffer can be allocated from the system memory. After allocating the graphics buffer from the system memory, it needs to be allocated The graphics buffer is mapped to the address space of the virtual memory corresponding to the application program, so that the application program can run normally. For multi-process applications, each process will first apply for a graphics buffer when it is running. Similarly, after the graphics buffer application is successful (that is, the system has enough memory allocated to the process), the graphics buffer needs to be mapped to the address space of the virtual memory corresponding to the process, so that the process can run normally.

2. Garbage collection (GC) mechanism

A mechanism to clear and recycle unused objects to release memory. When the application freezes and the response speed is slow (the memory usage is too high at this time. For example, for a 32-bit application, if the memory usage exceeds 3G, it will be judged as too high), the virtual machine will trigger garbage Recycling (GC) mechanism.

3. Low memory killer (LMK) mechanism

A memory cleaning mechanism of the Android system. The system regularly detects the memory usage of the application program. When the available memory of the system is low, the LMK mechanism is triggered to kill the low-priority process through the background to release the memory. Specifically, the priority of a process is judged by the oom_adj value of the process. The smaller the oom_adj value, the higher the priority, and the less likely the process will be killed when the LMK mechanism is triggered. It should be noted that the oom_adj value of the foreground process is 0, that is, the priority of the foreground process is the highest.

4. Virtual memory (virtual set size, VSS)

The size of all memory space addresses that a process can access. Theoretically, for 32-bit applications, the maximum virtual memory that can be used is 2 ³² , that is, 4G. In actual application, the system will reserve a small part, so for a 32-bit application, the maximum virtual memory that can be used is 3.7G, and if it exceeds 3.7G, it will cause memory overflow.

5. Memory overflow (out of memory, OOM)

There is unrecoverable memory or too much memory in the system, which eventually causes the memory used by the application to run larger than the maximum memory that can be provided. The memory overflow is manifested as an abnormal display of the application interface or a crash of the application.

In a software system, due to the improper use of resources such as pictures, objects, threads, files, and views, the resources are not released in time, which will lead to memory leaks, which in turn will cause memory overflow of the application, causing the application to freeze, and even the system to freeze. Case. In most cases, memory leaks are a cumulative process, and there will be no symptoms before problems occur, so it is difficult to find and locate them.

In practical applications, memory leaks can lead to the following situations:

1. The application freezes and responds slowly, triggering the garbage collection mechanism, resulting in application not responding (ANR) or application flashback.

2. Cause abnormal display of the application, unavailability of some functions of the application and other abnormalities.

Exemplarily, (a) in FIG. 1 is a schematic diagram of a display interface when application A is normally displayed when there is no memory leak. As shown in (b) in FIG. The abnormal display can be manifested as garbled characters; as shown in (c) in Figure 1, the abnormal display that occurs when the memory leak occurs in the above-mentioned application program A can be manifested as incomplete display; another example in Figure 1 As shown in (d), the display abnormality that occurs when the memory leak occurs in the above-mentioned application program A may be manifested as a situation where some functions are not displayed, and at this time, the part of the functions is in an abnormal state of being unavailable.

3. Abnormalities such as system crashes and freezes.

Exemplarily, when a user uses a mobile phone to watch a video, since the video playback application will continue to apply for memory and not release it during the video playback process, since the maximum available virtual memory of the video playback application is certain, so in After the usage limit of the virtual memory of the video playing application is reached, the requested memory cannot be mapped to the virtual memory of the video playing application. At the same time, the memory allocated by the system will be marked as used and cannot be allocated to other applications (processes), and memory mapping failure will cause the application to continue to apply for memory from the system, resulting in memory leaks. And because the available memory of the system is low, the LMK mechanism will be triggered, but because the video playback application is still running in the foreground, its priority is higher, so the video playback application will not be killed, so the occupied memory will not It will be released, which will eventually cause the entire system to crash and be stuck in an abnormal situation. When the system crashes and freezes, the user needs to force restart the mobile phone to restore normal use, which is troublesome to operate and will affect the user experience.

In practical applications, many applications are 32-bit applications, and when applying for system memory from the system, the application will apply for memory by continuously calling the graphicbufferallocator process interface. The maximum virtual memory that a 32-bit application can use is 4G. However, since the graphicbufferallocator process is a 64-bit process, when the virtual memory of the application exceeds 4G, it can still successfully apply for system memory from the system, and because the virtual memory of the application It has exceeded 4G, so the requested memory cannot be mapped to virtual memory, resulting in the system memory being requested but unable to be used, nor released. Moreover, after the memory mapping fails, the application will continue to apply for memory by calling the graphicbufferallocator interface, resulting in continuous memory leaks, which eventually lead to abnormal situations such as system crashes and freezing.

From the above description, we can see that once a memory leak breaks out, it will cause a variety of situations, and it is not easy to reproduce. That is to say, the problem of memory leak is difficult to find and solve, and the memory leak will seriously affect the use of users. Therefore, if the application programs that may cause memory leaks can be processed before the memory leaks cause abnormal situations, serious abnormalities such as system crashes and freezes can be avoided, and the impact on users can be reduced.

In view of the above-mentioned problems and user needs, the embodiment of the present application provides a management method of an application program. By monitoring the process of the application program to apply for a graphics buffer to the system memory, when the memory application fails and the virtual memory takes up too much In this case, activate the suicide recovery function to end all processes of the application to release the memory occupied by the application, avoid serious consequences such as system crashes and freezes caused by memory leaks, and reduce the impact on users.

The application management method provided by the embodiment of the application will be described in detail below in conjunction with the accompanying drawings. In the following description, for the purpose of illustration rather than limitation, specific details such as specific system structure and technology are proposed in order to thoroughly understand the application Example.

The execution subject of the above-mentioned application management method may be an electronic device, such as a mobile phone, a wearable device (such as a smart watch, a smart bracelet, smart glasses, smart jewelry, etc.), a tablet computer, a vehicle-mounted device, an augmented reality (augmented reality , AR)/virtual reality (virtual reality, VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (personal digital assistants, PDAs), and other electronic devices with network connectivity equipment.

鸿蒙系统(Harmony OS)或者其他操作系统的设备。上述电子设备也可以是其他电子设备，诸如具有触敏表面(例如触控面板)的膝上型计算机(laptop)等，本申请实施例对电子设备的具体类型不做任何限制。Exemplary embodiments of the aforementioned electronic devices include, but are not limited to

Devices with Harmony OS or other operating systems. The foregoing electronic device may also be other electronic devices, such as a laptop computer (laptop) with a touch-sensitive surface (eg, a touch panel), and the embodiment of the present application does not impose any limitation on the specific type of the electronic device.

Taking the above-mentioned electronic device as a mobile phone as an example, as shown in FIG. 2 , it is a schematic structural diagram of a mobile phone provided in an embodiment of the present application.

FIG. 2 shows a schematic structural diagram of the mobile phone 100 . The mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 11, an antenna 12, Mobile communication module 150, wireless communication module 160, audio module 170, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195 etc. . The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.

It can be understood that, the structure shown in the embodiment of the present invention does not constitute a specific limitation on the mobile phone 100 . In some other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. . Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

Wherein, the controller may be the nerve center and command center of the mobile phone 100 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thereby improving the efficiency of the system.

Exemplarily, the software system of the mobile phone 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the software structure of the mobile phone 100 is illustrated by taking the Android system with a layered architecture as an example. FIG. 3 is a block diagram of the software structure of the mobile phone 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer.

The application layer can consist of a series of application packages. As shown in Figure 3, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, bluetooth, video, and instant chat.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions. As shown in Figure 3, the application framework layer may include a window manager, a content provider, a view system, a process manager, a notification manager, a suicide recovery management module, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the download completion, message reminder, etc. The notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, emitting a prompt sound, terminal vibration, and indicator light flashing, etc.

The suicide recovery management module is an application program management mechanism that automatically scans and kills the application program to release the memory when it detects that the running application program satisfies the suicide recovery condition mentioned in the embodiment of the present application.

In the embodiment of the present application, the above suicide recovery condition may be memory application failure, the failure type is virtual memory mapping failure, and the virtual memory occupied by the application exceeds a preset threshold.

In the embodiment of the present application, the above-mentioned automatic killing of the application program may directly end all processes of the application program. At this time, the display interface of the mobile phone 100 will directly jump to the main screen interface showing the mobile phone 100, that is, the user feels The application program flashes back; the above-mentioned automatic killing of the application program can also be to automatically pull up the main process of the application program after ending all processes of the application program. At this time, the display interface of the mobile phone 100 will directly jump to the application program main display interface. Since the interval time for pulling up the main process of the application program after the process of the application program is terminated is very short, the user has no perception of this, and can only feel that the display interface of the mobile phone 100 jumps back to the main display interface of the application program.

In some embodiments of the present application, the suicide recovery management module also has a memory application monitoring function, which can automatically enable the memory application monitoring function when an application program sends a memory application to the system memory, so as to monitor whether the memory application is successful.

Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as target life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

The application program management method provided by the embodiment of the present application can run in the application program framework layer, that is, the above application program management method can be implemented through the suicide recovery management module in the application program framework layer.

The application program management method provided by the embodiment of the present application can be applied to various usage scenarios where memory leaks exist. For example, the application management method provided by the embodiment of the present application can be applied to scenarios where a user watches a video using an electronic device or uses an instant chat software to view pushed articles.

For example, when a user uses an instant chat software to view a push article (it may be a news push article/video, etc.), the process of the application program will apply for a graphics buffer from the system memory for the display drawing of the interface and the storage of display drawing data. When the application process initiates a graphics buffer application to the system memory, the mobile phone starts the memory application monitoring function, and when it detects that the instant chat software meets the suicide recovery conditions (at this time, the graphics buffer application fails, and the failure type is virtual memory mapping failure. , and the virtual memory occupied by the application exceeds the preset threshold), start suicide recovery, so that the application can release memory, and avoid the situation that causes the entire mobile phone system to crash and freeze.

Exemplarily, as shown in FIG. 4 , it is a schematic diagram of some graphical user interfaces (graphical user interface, GUI) that may be involved in the first application scenario.

In some embodiments, the interface of the instant chat software includes a main display area 10 (the interface corresponding to "information"), and other functional areas 20 (such as "contacts", "dynamics" and the like in (a) of Figure 4 ) , subdialog 30. The main display area 10 will display a plurality of sub-dialogues 30, specifically, it may be displayed in the form of (a) in FIG. 4 . When the user wants to view the article pushed by a certain sub-dialogue, he can click the control corresponding to the sub-conversation (such as the sub-conversation of contact 1), so that the display interface of the instant chat software jumps to the display interface corresponding to the sub-conversation (such as (b) in Figure 4).

In some embodiments, as shown in (c) in Figure 4, when the application program is running, for example, when the user clicks on a certain sub-dialog to view the dialog, when the process corresponding to the sub-dialog needs to apply for a graphics buffer At this time, the mobile phone may display a prompt message, prompting the user whether to enable the memory application monitoring function of the mobile phone. The prompt message is, for example, "This operation may cause a memory leak. Do you want to enable the memory application monitoring function to ensure the normal operation of the system?". When the mobile phone receives the user's confirmation of enabling the operation of the memory application monitoring function (such as the user clicking the "confirm" icon shown in (c) in Figure 4), the memory application monitoring function can be enabled, and the memory application monitoring function can be applied to the process. The process is monitored.

In some embodiments, after the mobile phone obtains the application result of the image buffer, if the application is successful, the application continues to run normally; if the application fails, the reason for the application failure is further analyzed. If it fails, the size of the virtual memory occupied by the application can be further obtained, and when the size of the virtual memory occupied by the application exceeds a preset threshold, the suicide recovery function is activated.

In some embodiments, when the mobile phone starts the suicide recovery function, all processes of the application program can be ended directly, and at this time, the display interface of the mobile phone will jump back to the main screen interface of the mobile phone (as shown in (d) in Figure 4 interface).

Or, when the mobile phone starts the suicide recovery function, it can also automatically pull up the main process of the application program after ending all processes of the application program, so that the display interface of the mobile phone displays the main display interface of the application program (as shown in Figure 4 (a) shows the interface).

It can be understood that the interface shown in FIG. 4 is only an example, and the embodiment of the present application does not limit the specific content displayed on the interface (such as the specific content of the prompt information), the display position of the prompt information, and the like. For example, in order not to affect the user's viewing of information, the prompt information shown in FIG. 4 may also be set as a prompt in the status bar, and an information mark is displayed to remind the user that relevant information is available for viewing. When users need to view, they can pull down the status bar and click related information to view. Alternatively, relevant information may also be displayed in the form of a small window in the lower right corner or upper right corner of the instant chat interface, etc., so as to remind the user while reducing the occlusion of the chat content and reducing the impact on the user.

It should be noted that the ways for the mobile phone to activate the memory application monitoring function may include: a method for the user to actively enable the memory application monitoring function, a method for the mobile phone to automatically enable the memory application monitoring function, and a method for enabling the memory application monitoring function by default.

Method 1, the user actively enables the memory application monitoring function

Exemplarily, as shown in FIG. 5 , it is a schematic diagram of some graphical user interfaces involved in the process of enabling the memory application monitoring function provided by the embodiment of the present application. Here, the electronic device is a mobile phone as an example.

In some embodiments, when the application program starts to run and its process initiates an application for creating a graphics buffer to the system memory, the mobile phone may prompt the user to enable the memory application monitoring function. The way of prompting the user may be, for example, the way of displaying prompt information on the interface (as shown in (c) in FIG. 4 ), or through voice; or through the combination of interface display and voice.

Exemplarily, as shown in (a) in FIG. 5 , it is a schematic diagram of a main screen interface of a mobile phone. The home screen interface may include an application icon display area 51 for displaying multiple types of application (application, App) icons, such as a clock icon, a calendar icon, a gallery icon, a memo icon, a file management icon, an email icon, a music icon, etc. icon, calculator icon, voice recorder icon, sports health icon, instant chat icon, browser icon, settings icon, etc. There may be a page indicator display area 52 under the multiple application program icons, and the page indicator included in the area is used to indicate the positional relationship between the currently displayed page and other pages. A tray application icon display area 53 may be displayed below the page indicator, for displaying a plurality of tray application icons, such as a camera application icon, an address book application icon, a phone dial application icon, an information application icon, and the like. In some other embodiments, the main screen interface of the mobile phone may include more or less application program icons or tray application icons than shown in the figure, which is not limited in this application. A status bar 54 can also be displayed on the top of the main screen interface, and the status bar 54 can include: one or more signal strength indicators of the mobile communication signal (or cellular signal), the battery indicator of the mobile phone, and the time indicator Wait.

In some embodiments, the mobile phone can receive the user's click operation on the setting icon; in response to the user's click operation, the mobile phone can display the setting details interface as shown in (b) in FIG. 5 .

As shown in (b) in Figure 5, the setting details interface may include multiple business management columns, such as wireless and network management columns, Bluetooth management columns, desktop and wallpaper management columns, display management columns, sound management columns, application management bar, battery management bar, storage management bar, security and privacy management bar, etc. In practical applications, the setting interface may also include more or fewer types of management columns than those shown in the illustration, which is not limited in this application.

In some embodiments, the mobile phone may receive the user's click operation on the application management bar; in response to the user's click operation, the mobile phone may display the application program management interface as shown in (c) in FIG. 5 .

Exemplarily, the application program interface may include a plurality of service management columns, and the services include, for example: system application setting, application monitoring management, application dual opening, authorization management, and the like. Behind each service name, a next page indicator corresponding to the service may be displayed.

In some embodiments, as shown in (c) of FIG. 5 , the mobile phone may receive a click operation of the next page indicator in the application monitoring management bar. In response to the user's click operation, the mobile phone may display an application monitoring management interface as shown in (d) in FIG. 5 .

Exemplarily, as shown in (d) of FIG. 5 , the application monitoring management interface may include description content of the memory application monitoring function, switch controls, and a personalized setting area for each application under the memory application monitoring function. Wherein, the description content of the memory application monitoring function is used to introduce the memory application monitoring function, so that the user can understand the function of the function more clearly. The content of the description may be, for example, "after the memory application monitoring function is turned on, the system will monitor the result of the running application program applying for system memory, so as to detect memory leaks in time". In some embodiments, the lower area of the introduction of the memory application monitoring function may display a switch control corresponding to the memory application monitoring function, so as to allow the user to enable or disable the memory application monitoring function.

It should be understood that by independently setting the controls for controlling the on/off of the memory application monitoring function for different applications, this enables the user to selectively use the memory application monitoring function in combination with the characteristics of the application programs and more in line with requirements. In this way, on the basis of considering different business characteristics, the function can be applied more reasonably, and the memory application monitoring function can avoid interference or interruption of the process of some application programs, thereby ensuring the user experience.

Method 2, the mobile phone automatically turns on the memory application monitoring function

In a possible implementation, when the application starts running, the mobile phone can automatically enable the memory application monitoring function, or when the application process initiates a memory application to the system memory (applying for a graphics buffer), the mobile phone can automatically open the memory The application monitoring function monitors the status of the memory application.

Optionally, when the memory application monitoring function is enabled on the mobile phone, a prompt message may be displayed to inform the user that the mobile phone will currently execute the application monitoring function. Alternatively, query information may also be displayed to ask the user whether to confirm that the mobile phone executes the memory application monitoring function (as shown in (c) in FIG. 4 ). Exemplarily, the prompt information or query information may be displayed in the status bar of the mobile phone, or displayed in the current interface of the mobile phone, which is not limited in this application.

It should be understood that the process of the mobile phone automatically enabling the memory application monitoring function in this manner may be unaware to the user. In this way, the memory application monitoring function can avoid impacting the currently running applications, such as avoiding video pauses, etc., thereby ensuring user experience.

Method 3, the memory application monitoring function is enabled by default

In a possible implementation, before the mobile phone leaves the factory, the memory application monitoring function can be set to be enabled by default, so that the memory application can be monitored and managed at any time during the subsequent use of the mobile phone by the user.

In combination with the exemplary opening methods described above, the memory application monitoring method provided by the embodiment of this application can be processed in a form that the user is aware of (for example, the user actively opens it, or displays relevant information to the user, etc.), or it can also be performed without the user. It is performed in the form of perception, which is not limited in this embodiment of the present application.

The application scenarios to which the application program management method provided in the embodiment of the present application is applicable, the way to enable corresponding functions, etc. are introduced above with reference to the accompanying drawings. In order to better understand the signal strength prediction method provided by the embodiment of the present application, the specific implementation process thereof is exemplarily introduced below with reference to the accompanying drawings.

Exemplarily, as shown in FIG. 6 , it is a schematic diagram of an interaction flow within the system of the electronic device during the process of executing the application program management method provided by the embodiment of the present application by the electronic device provided in the embodiment of the present application. Specifically, the following steps may be included:

S601. During the running of the application program, the process of the application program applies for a graphics buffer from the memory manager.

Wherein, the above-mentioned application program may be a multi-process application program or a single-process application program. In practical applications, in order to improve the running speed and reduce the redundancy of the application program, the application program is usually a multi-process application program, and a master-slave relationship can be established between multiple processes.

During the running of the application, in order to draw the interface and save the drawn data, the running process will apply for a graphics buffer (graphic buffer) from the memory manager. Taking the Android system as an example, the above process can apply for a graphic buffer to the memory manager. The following way:

Method 1: Apply for a graphics buffer shared between processes through graphicbuffermapper.

The Android system provides the graphicbuffermapper tool class, which provides an interface for the upper layer to access the hardware abstraction layer (gralloc module).

When the application in user space uses the graphics buffer, it needs to load the gralloc module first, and obtain a gralloc device and a fb device. After the gralloc device is available, the application in the user space can apply for the allocation of a graphics buffer, and Map this graphics buffer into the address space of the application program, so that the content of the picture to be drawn can be written into it. Finally, the application program in the user space renders the prepared graphics buffer to the frame buffer through the fb device, that is, draws the content of the graphics buffer to the display screen to realize the interface display of the application program.

Method 2: Apply for the graphics buffer used by the application through the graphicbufferallocator process interface.

The Android system also provides a graphicbufferallocator process interface, through which the image buffer can be commonly applied for.

S602, the suicide recovery management module starts a memory application monitoring function.

Here, after the suicide recovery management module starts the memory application monitoring function, it will send an instruction to obtain the application result of the graphics buffer application to the memory manager.

In some embodiments, the suicide recovery management module can start the memory application monitoring function when the application program starts to run, and can also start the memory application monitoring function when the process of the application program initiates a graphics buffer application to the system memory. Suicide recovery management The module can also obtain the virtual memory usage of the application in real time. When the virtual memory usage of the application exceeds a certain value (this value can be set according to the actual application scenario, this application does not limit this), open the memory application The monitoring function can also start the memory application monitoring function when the virtual memory usage of the application exceeds a certain value and the application process initiates a graphics buffer application. Of course, the memory application monitoring function can also be activated under other circumstances. The application does not elaborate on this.

Wherein, the above-mentioned method of starting the memory application monitoring function can refer to the above-mentioned related content, and in order to avoid repetition, details are not repeated here.

Here, the application results of the above graphics buffer application include application success and application failure.

Application results can be expressed in binary coded form. For example, the application result may include two fields, one field is used to indicate whether the application is successful, and the other field is used to indicate the corresponding error type when the application fails. Exemplarily, the field used to indicate whether the application is successful includes 2 bits, wherein 00 indicates that the application is successful, and 01 indicates that the application fails; the corresponding failure type used to indicate that the application fails includes 3 bits, wherein 001 indicates that the available memory of the system is too large. Less, 010 means memory mapping failure, 011 means other abnormal conditions, etc. (when the first field is 00, the corresponding second field is 000).

Of course, the above application result may also include only one field, which can indicate whether the application is successful or not, and can also indicate the corresponding failure type when the application fails. Exemplarily, this field includes 4 bits, of which the first bit is used to indicate whether the application is successful, and the second to fourth bits are used to indicate the corresponding failure type when the application fails. For example, 0000 means that the application is successful, and 1001 means that the application is failed. And the failure type is too little available memory in the system, 1010 means that the application failed and the failure type is memory mapping failure, and 1011 means that the application failed and the failure type is other abnormal conditions.

Of course, when the application is successful, no_error can be returned; when the application fails, error can be returned with an error code, which indicates the type of failure.

It can be understood that the above is only an example of the application results, and the above application results may also include other content, such as the return time, etc., which is not limited in this application.

S603, the memory manager sends the application result of the image buffer application to the suicide recovery management module in response to the above instruction of acquiring the application result of the graphics buffer application.

Specifically, when the application process sends an image buffer application to the system memory, when the available memory of the system satisfies the application, and the applied memory can be mapped to the address of the virtual memory of the process, the memory manager will send the application successful Results are sent to the Suicide Recovery Management Module.

When the available memory of the system is too small (the memory occupied by the requested graphics buffer is larger than the available memory of the system), the requested memory cannot be mapped to the address of the virtual memory of the process, or other abnormal conditions, the memory manager will report the result of the application failure Sent to the Suicide Recovery Administration Module.

It should be noted that if the application process applies for the graphics buffer through the method 2 in S601, that is, when applying for the graphics buffer used by the application through the graphicbufferallocator process interface, although for the process, the graphics buffer The application failed, but in fact the memory manager has allocated the memory required by the graphics buffer it applied for to the process, and the process will continue to initiate the application after the application fails, so that the memory allocated by the system (actually Not being used) will accumulate more and more, and eventually lead to insufficient system memory, and the whole machine crashes and freezes.

S604, the suicide recovery management module detects that the application result of the received graphics buffer application is successful, and then the suicide recovery management module sends a mapping instruction to the application program.

S605, the application program maps the requested memory to the address of the virtual memory of the process of the application program in response to the mapping instruction.

After the suicide recovery management module receives the application result sent by the memory manager, it can determine whether the graphics buffer application is successful by analyzing the binary code corresponding to the application result. Exemplarily, when the application result includes two fields, wherein the first field is used to indicate whether the application is successful, the code of this field is read, and the graphics buffer application result can be determined based on the code of this field.

For example, if the application result received by the suicide recovery management module is "00,000", it reads the content "00" in the first field, and according to the predetermined meaning corresponding to the code, the application result is successful. For another example, if the application result is "01,010", then the read content of the first field is "01". According to the meaning corresponding to the predetermined code, the application result is application failure.

As another example, when the application result contains only one field, where the first bit of the field is used to indicate whether the application is successful, the code of this bit is read, and the application result of the memory application is determined based on the code of this bit.

For example, if the application result is "0000", read the code "0" in the first digit, and according to the predetermined meaning corresponding to the code, it can be known that the application result is a successful application. For another example, if the application result is "1010", read the first code "1", and according to the predetermined meaning corresponding to the code, the application result is application failure.

Among them, the memory mapping process in which the application program maps the requested memory to the address of the virtual memory of the process is a commonly used memory management method. The specific memory mapping process can be implemented by referring to the existing methods, and this application does not describe it here. To repeat.

S606. The suicide recovery management module detects that the application result of the received graphics buffer application is application failure, and analyzes the failure type according to the application result.

The process for the suicide recovery management module to determine that the application result of the memory application is application failure can refer to the description of S604, and will not be repeated here to avoid repetition.

Wherein, the failure types when the above application fails may include too little available memory in the system, memory mapping failure, other abnormal conditions, etc., which are not limited here.

In some embodiments, the suicide recovery management module can determine the failure type according to the application result returned by the memory manager. For example, the type of failure can be determined by analyzing the code corresponding to the 2 of the application result.

Exemplarily, when the application result includes two fields, the first field is used to indicate whether the application is successful, and the second field is used for the type of failure, indicating that the code of the second field is read and based on the code of the second field The memory application result can be determined.

For example, if the application result is "01,001", read the content "001" in the second field, and according to the predetermined meaning corresponding to the code, it can be known that the failure type is too little available memory in the system. For another example, if the application result is "01,010", the read content of the second field is "010". According to the meaning corresponding to the predetermined code, the failure type is a memory mapping failure.

As another example, when the application result only contains one field, where the 2nd to 4th digits of the field are used to indicate the type of failure, then read the codes of the 2nd to 4th digits, based on the second to 4th digits The encoding of the bit determines the application result of the memory application.

For example, if the application result is "1001", read the code "001" from the second to the fourth digit, and according to the predetermined meaning corresponding to the code, it can be known that the failure type is too little available memory in the system. For another example, if the application result is "1010", read the code "010" from the 2nd to 4th digits. According to the predetermined meaning corresponding to the code, it can be known that the failure type is memory mapping failure.

For another example, when the application result is returned as an error with an error code, the failure type can be determined through the error code.

S607. The suicide recovery management module sends a first exception log output instruction to the log manager when determining that the failure type is not a memory mapping failure.

For the related content of judging the failure type, refer to the description of S606, which will not be repeated here.

S608. The log manager generates and saves an exception log corresponding to the failure type in response to the first exception log output instruction.

Here, the above-mentioned first exception log output instruction is used to instruct the log manager to generate and save the exception log corresponding to the failure type.

Since the failure type is not a memory mapping failure, it will basically not cause memory leaks, so there is no need to perform any operations on the application, only need to control the log manager to generate and save the exception log corresponding to the failure type, so that users Know the failure type of the graphics buffer application failure, and other related information (such as application time, application subject (that is, which process of which application program submitted the application), etc.).

In some embodiments, the above-mentioned exception log may include the name of the process initiated by the application, the time when the exception occurred, and the content of the exception. The content of the exception includes the failure to apply for the graphics buffer and the type of failure. Exemplarily, when the failure type is too little available memory in the system, the above abnormal content may be that process B of application A fails to apply for a graphics buffer at time xx due to too little system memory.

In some embodiments, when the failure type is too little system memory, based on the exception log, the electronic device can start the LMK mechanism.

In some embodiments, the above exception log may be stored in a log manager, and the electronic device may read the exception log through the log manager.

S609. The suicide recovery management module obtains the virtual memory occupation of the application program in the case that the failure type is determined to be a memory mapping failure.

When the failure type is memory mapping failure, it is very likely that the virtual memory of the application is too much, which can easily lead to system memory leaks. In order to determine whether it is due to too much virtual memory, you can obtain The application's virtual memory usage, and then analyze whether there is a risk of memory leaks.

In some embodiments, the suicide recovery management module can call out the virtual memory usage of the application through the /proc/self/status function. After it is determined that the memory application fails and the failure type is a memory mapping failure, the /proc/self/status function is automatically called to obtain the current virtual memory usage of the application.

S610. The suicide recovery management module determines whether the virtual memory occupied by the application exceeds a preset threshold.

Wherein, the preset threshold can be set according to the application program, for example, for a 32-bit application program, the above preset threshold can be set to 3.7G. Of course, for 32-bit applications, the above preset threshold can be set to some value lower than 3.7G, such as 3.5G, 3.2G and so on.

S611. The suicide recovery management module sends a second exception log output instruction to the log manager when it is determined that the virtual memory occupied by the application program does not exceed a preset threshold.

S612. In response to the second exception log output instruction, the log manager generates and saves an exception log indicating that the memory mapping fails and the virtual memory does not exceed the threshold.

Here, the above-mentioned first exception log output instruction is used to instruct the log manager to generate and save the exception log in which the memory mapping fails and the virtual memory does not exceed the threshold.

Here, since the virtual memory occupied by the application does not exceed the preset threshold, that is to say, this will not cause a memory leak, there is no need to perform any operations on the application except to generate and save the memory map through the log manager. Exception logs that the memory does not exceed the threshold.

S613. The suicide recovery management module sends an instruction to start the suicide recovery function to the process manager when it is determined that the virtual memory occupied by the application exceeds a preset threshold.

S614, the process manager terminates all processes of the application program in response to the instruction for starting the suicide recovery function.

In some embodiments, when the virtual memory occupied by the application program exceeds the preset threshold, the suicide recovery management module may send an instruction to the process manager to start the suicide recovery function, and the instruction is used to instruct the process manager to terminate the application program. All processes, frees system memory occupied by the application.

The process manager contains all the processes currently running in the system, and the system memory occupied by the application can be released by ending all the processes related to the application name through the process manager.

In some embodiments, when the electronic device activates the suicide recovery function, all processes of the application program can be terminated directly. At this time, the display interface of the electronic device will jump back to the main screen interface of the electronic device, that is, the user feels that the application program has flashed back. .

In some embodiments, after the process manager terminates all processes of the application program, the log manager may also generate and save an exception log indicating that the application program is terminated due to high virtual memory usage.

According to the application program management method provided by the embodiment of the present application, by monitoring the application process of the application program to the memory manager for the graphics buffer, when the memory application fails due to excessive virtual memory usage, the suicide recovery function is activated, End all processes of the application to release the memory occupied by the application, avoid serious consequences such as system crashes and freezes caused by memory leaks, and reduce the impact on users.

The above embodiment will cause the application program to crash directly, resulting in poor experience on the user side. In order to reduce the impact on the user's use, another embodiment of the present application also provides an application program management method, as shown in Figure 7, which is the The embodiment provides a schematic diagram of another interaction flow in the system of the electronic device when the electronic device executes the application program management method provided in the embodiment of the present application. Specifically, the following steps may be included:

For the content of S701-S712, refer to the content of S601-S612, and to avoid repetition, details are not repeated here.

S713. The suicide recovery management module determines whether the process that initiates the graphics buffer application is the main process when it is determined that the virtual memory occupied by the application exceeds a preset threshold.

Here, the suicide recovery management module may determine whether the process (currently running process) that initiates the graphics buffer application is the main process through the ID of the process.

Each process has its own ID, and the ID of the main process is obviously different from the ID of the child process. Therefore, it can be determined whether it is the main process or the child process through the ID of the process.

S714, when the suicide recovery management module determines that the process that initiates the graphics buffer application is not the main process, sends an instruction to terminate all processes of the application program to the process manager.

S715. The process manager terminates all processes of the application program in response to the instruction to terminate all processes of the application program.

Since the process that initiates the graphics buffer application is not the main process, the interface displayed by the electronic device at this time is not the display interface of the main process of the application program. It may be a page that the user enters after multiple operations, and the electronic device cannot reset Therefore, the electronic device will only end all processes of the application program through the process manager to release the system memory occupied by it.

For the implementation process of terminating all the processes of the application program, refer to the description of S614, and to avoid repetition, details are not repeated here.

S716. In the case that the suicide recovery management module determines that the process that initiates the graphics buffer application is the main process, send an instruction to the process manager to restart all the processes of the application program and restart the main process of the application program.

S717, the process manager responds to the above instruction to restart the main process of the application program after ending all the processes of the application program, and restarts the main process of the application program after ending all the processes of the application program.

Since the process that initiates the graphics buffer application is the main process of the application program, the interface displayed by the electronic device is the main display interface of the application program at this time. The main process, at this time, the display interface of the electronic device will directly jump to the main display interface of the application program.

Since the time interval between launching the main process of the application program after the process of the application program is terminated is very short, the user is not aware of this, and can only feel that the display interface of the electronic device jumps back to the main display interface of the application program. At this time, the user will not experience the crash of the application program, so the system memory occupied by the application program can be released while the impact on the user's use can be avoided, and the user experience can be improved.

The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when it is run on a computer or a processor, the computer or the processor executes one of the above-mentioned methods or multiple steps.

The embodiment of the present application also provides a computer program product including instructions. When the computer program product is run on the computer or the processor, the computer or the processor is made to perform one or more steps in any one of the above methods.

The embodiment of the present application also provides a chip system including instructions. When the instruction is executed on the computer or the processor, the computer or the processor is caused to perform one or more steps in any one of the above-mentioned methods.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted via a computer-readable storage medium. The computer instructions may be transmitted from one web site, computer, server, or data center to another web site, computer, server or data center for transmission. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)) and the like.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments are realized. The processes can be completed by computer programs to instruct related hardware. The programs can be stored in computer-readable storage media. When the programs are executed , may include the processes of the foregoing method embodiments. The aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store program codes.

The above is only the specific implementation of the embodiment of the application, but the protection scope of the embodiment of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the embodiment of the application shall be covered by this application. Within the scope of protection of the application examples. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims (10)

1. A method for managing an application program, comprising:

monitoring the application result of the graphic buffer area in the running process of the application program;

if the application result of the image buffer area is application failure, analyzing the failure type according to the application result;

if the failure type is memory mapping failure, acquiring the virtual memory occupation condition of the application program;

and if the virtual memory occupied by the application program exceeds a preset threshold value, starting a suicide recovery function of the application program.

2. The method for managing an application according to claim 1, wherein if the virtual memory occupied by the application exceeds a preset threshold, the method for starting a suicide recovery function includes:

and when the virtual memory occupied by the application program exceeds a preset threshold value, ending all processes of the application program.

3. The method for managing application programs according to claim 1, wherein if the virtual memory occupied by the application program exceeds a preset threshold, the method for starting suicide recovery function comprises:

when the virtual memory occupied by the application program exceeds a preset threshold value, judging whether the process applying for the graphic buffer area is a main process of the application program;

if the process applying for the graphic buffer area is the main process of the application program, finishing all the processes of the application program and then re-pulling up the main process of the application program; otherwise, all processes of the application program are ended.

4. The method for managing an application program according to claim 1, wherein after monitoring the application result of the graphics buffer during the running of the application program, the method further comprises:

and if the application result of the graphic buffer area application is successful, mapping the applied memory to the address of the virtual memory of the process.

5. A method for managing an application program according to any one of claims 1 to 4, further comprising:

and if the failure type is not the memory mapping failure, outputting an abnormal log corresponding to the failure type.

6. A method for managing an application program according to claim 1, further comprising:

and if the virtual memory occupied by the application program does not exceed the preset threshold, outputting an abnormal log which fails in memory mapping and does not exceed the threshold.

7. A method for managing an application program according to claim 2 or 3, further comprising:

and after finishing all processes of the application program, outputting an abnormal log for finishing the operation of the application program due to overhigh virtual memory occupation.

8. The method for managing application programs according to claim 1, wherein the monitoring of the application result of the graphics buffer during the running of the application program comprises:

when the process of the application program initiates the application of the graphic buffer area, the memory application monitoring function is started to obtain the application result of the graphic buffer area.

9. An electronic device, comprising a processor and a memory, the processor and the memory being coupled, the memory being configured to store a computer program which, when executed by the processor, causes the electronic device to carry out the steps of the method of any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a computer program which, when run on a computer, causes the computer to carry out the steps of the method according to any one of claims 1 to 8.

Images