WO2023185684A1

WO2023185684A1 - Process killing method for application, and electronic device

Info

Publication number: WO2023185684A1
Application number: PCT/CN2023/083751
Authority: WO
Inventors: 季柯丞; 杨文飞; 常演; 王绪
Original assignee: 华为技术有限公司
Priority date: 2022-04-01
Filing date: 2023-03-24
Publication date: 2023-10-05
Also published as: CN116933254A

Abstract

A process killing method for an application, and an electronic device, relating to the field of operating systems and being capable of preventing an electronic device from frequently triggering a process killing operation and facilitating the improvement of the running fluency and stability of an electronic device. The method comprises: an electronic device calculating statistics on a first-type memory and a second-type memory occupied by running processes, wherein the first-type memory comprises one or more of a file page occupied memory, a core-library file occupied memory, a cache data occupied memory, and a user-mode anonymous page occupied memory, and the second-type memory comprises one or more of streaming media occupied memory and a kernel occupied memory; and if it is detected that a memory of the electronic device meets a preset condition, determining a target process from the running processes according to the first-type memory and the second-type memory occupied by the processes, and killing the target process.

Description

Process checking and killing method of application program and electronic device

This application requires the priority of the Chinese patent application submitted to the State Intellectual Property Office on April 1, 2022, with the application number 202210339419.4 and the application title "A method for killing application processes and electronic equipment", and its entire content has been approved This reference is incorporated into this application.

Technical field

The present application relates to the field of operating systems, and in particular, to an application process checking and killing method and an electronic device.

Background technique

When memory resources are tight, electronic devices can use process scanning and killing methods to clean up the memory occupied by processes. Taking interactive operating systems (such as Android systems) as an example, electronic devices usually clean up the memory occupied by processes that are not commonly used or will not be used in the short term based on the user's usage habits. However, in actual usage scenarios, the memory released after each process killing does not account for a high proportion of the entire machine's memory. Therefore, electronic devices need to frequently trigger process killing behaviors, which can easily cause system crashes.

Contents of the invention

This application provides a process checking and killing method for an application program and an electronic device, which can prevent electronic devices from frequently triggering process checking and killing behaviors, and is conducive to improving the smoothness and stability of the operation of electronic devices.

In order to achieve the above objectives, the embodiments of the present application provide the following technical solutions:

The first aspect provides a process checking and killing method for application programs. The method includes: an electronic device runs one or more application APPs; the electronic device counts the first type of memory and the second type of memory occupied by each process started by one or more APPs. Class memory, the first class of memory includes one or more of the memory occupied by file pages, core library files, cached data, and user-mode anonymous pages; the second class of memory includes the memory occupied by streaming media and the kernel Occupying one or more items in the memory; when it is detected that the memory of the electronic device meets the preset conditions, the electronic device determines from the processes started by one or more APPs based on the first type of memory and the second type of memory occupied by each process. Target process; electronic device killing target process.

That is to say, when counting the memory occupied during the running of the process, the first type of memory and the second type of memory occupied during the running of the process are also counted, that is, the total occupation of the first type of memory and the second type of memory is counted. Then, when the electronic device performs process killing, it will determine the target process based on the total occupation of the first type of memory and the second type of memory of each candidate process. Moreover, after killing the target processes, the electronic device will reclaim the first type of memory and the second type of memory occupied by these target processes. Since the first type of memory and the second type of memory recovered through this method account for a high proportion of the entire machine memory, it is conducive to maintaining the available memory of the electronic device at a higher value and preventing the electronic device from frequently triggering process checks. Killing behavior is conducive to improving the smoothness and stability of the operation of electronic devices.

In a possible implementation, the memory of the electronic device meeting the preset conditions includes: the remaining memory amount of the electronic device is less than or equal to the first threshold, and the blocking duration of the process in the electronic device due to untimely memory allocation is greater than or equal to the second threshold. Threshold, the total occupied amount of the second type of memory in the electronic device is greater than or equal to any of the third thresholds.

In some embodiments, the electronic device may use a waterline triggering mechanism based on the amount of remaining memory to kill processes. Specifically, the electronic device can monitor the amount of remaining memory of the electronic device, where the remaining memory refers to available memory, which can include free memory in the system, as well as memory occupied by file pages, core library files, and cached data. when monitoring When the amount of remaining memory is less than or equal to the threshold 1, the electronic device starts the process killing process.

In other embodiments, the electronic device may also use a triggering mechanism based on Pressure Stall Information (PSI) to kill the process. Specifically, the electronic device can monitor the blocking time caused by untimely memory allocation when each process on the electronic device is running, that is, the time the process waits for memory allocation. When it is detected that the blocking time of the process is greater than or equal to the threshold 2, the process killing process is started.

In some embodiments, the electronic device can also use a waterline triggering mechanism based on the second type of memory usage to kill the process. Specifically, the electronic device can monitor the total occupied amount of the second type of memory in the electronic device. When it is detected that the total occupied amount of the second type of memory is greater than or equal to the threshold 3, the electronic device starts the process killing process.

It should be noted that this embodiment provides a method of monitoring the memory occupancy of an electronic device from the perspective of monitoring the second type of memory occupancy. In the actual use of electronic devices, the second type of memory occupancy is usually large, which is one of the main reasons for the memory shortage of electronic devices. Therefore, the startup process killing process is determined from the perspective of monitoring the second type of memory occupancy. Being able to more accurately monitor the memory usage of electronic devices is more conducive to fundamentally solving the problems of high memory pressure and slow system operation caused by high second-type memory usage of electronic devices. In addition, since this embodiment realizes the function of recycling the second type of memory, it effectively reduces the occupation of the second type of memory, which helps the system's available memory to stay at a higher threshold for a long time, ensuring the stability and smoothness of the system operation. .

In a possible implementation, the first type of memory and the second type of memory occupied by the first process include the first type of memory and/or the second type of memory occupied by the second process called by the first process. Any one of the processes started for one or more APPs, and the second process is not called by other processes except the first process. The electronic device determines the target process from the processes started by one or more APPs based on the first type of memory and the second type of memory occupied by each process, including: after the electronic device determines that the first process is the target process, it determines that the second process is also target process.

For example, in a scenario where there are linkages between multiple processes running on an electronic device, the electronic device can also determine other processes called by the target process based on the target process and the linkage relationships between different processes maintained by the electronic device, and determine These other processes are also processes that need to be killed, that is, they are also target processes. It can be understood that after the target process (for example, the first process) is checked and killed, if other processes (such as the second process) called by the target process are only called by the target process, then these other processes can also be checked and killed. Memory occupied by other processes can also be reclaimed. This will help further improve memory utilization and improve the system's operating speed. Of course, if other processes called by the target process are also called by other non-target processes, these other processes cannot be killed to ensure the normal operation of other non-target processes.

In a possible implementation, after the electronic device kills the target process, the method further includes: the electronic device determines whether the first component associated with the target process is a key component; where the key component is a component containing key information, and the key information Including information that will affect the stability of the system operation or the user experience when the target process is running; if it is determined that the first component is a critical component, the electronic device retains the information of the first component; if it is determined that the first component is not a critical component, The electronic device then clears the information of the first component.

Consider that when selecting a target process, some processes with higher priority or system level may be determined as target processes. In order to ensure the stability of the system operation or ensure the user experience, during the process of killing the target process, the key components in the target process are identified (that is, the information in the key components affects the stability of the system or the user experience) , and preserve key components in the target process. Later, when restarting the target process (or restarting the APP corresponding to the target process), you can directly use the retained key components to restore the target process to ensure that the system Operation stability or ensuring user experience.

In a possible implementation manner, the key information includes one or more of the information on the negative screen, the information on the magazine lock screen, the information displayed on the active screen, the information on the weather widget, and the reading progress information of the electronic document.

In a possible implementation, after the electronic device kills the target process and after the electronic device retains the information of the first component, the method further includes: the electronic device calls the first component; when it is queried that the electronic device retains the first component After receiving the information of the component, the electronic device starts the third process; the electronic device establishes an association between the third process and the first component based on the retained information of the first component.

In a second aspect, an electronic device is provided, including: a processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, the processor The computer instructions are read from the memory, so that the electronic device performs the method described in the above aspect and any possible implementation manner therein.

A third aspect is to provide a device, which is included in an electronic device and has the function of realizing the behavior of the electronic device in any of the above aspects and possible implementation methods. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above functions. For example, detection module or unit, statistical module or unit, determination module or unit, and killing module or unit, etc.

The fourth aspect is to provide a computer-readable storage medium. The computer-readable storage medium includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to perform the above aspects and any possible implementation manner thereof. the method described.

A fifth aspect provides a chip system, including a processor. When the processor executes instructions, the processor executes the method described in the above aspects and any of the possible implementations.

In a sixth aspect, a computer program product is provided. When the computer program product is run on a computer, it causes the computer to execute the method described in the above aspects and any of the possible implementations.

The technical effects achieved by the electronic equipment provided by the second aspect, the device provided by the third aspect, the computer-readable storage medium provided by the fourth aspect, the chip system provided by the fifth aspect, and the computer program product provided by the sixth aspect , reference may be made to the description of technical effects in the above first aspect and possible implementations in the first aspect, which will not be described again here.

Description of drawings

Figure 1 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application;

Figure 2A is a schematic diagram of the software structure of an electronic device provided by an embodiment of the present application;

Figure 2B is a schematic diagram of memory occupied by a process of an application provided by an embodiment of the present application;

Figure 3 is a schematic flowchart of an application process checking and killing method provided by an embodiment of the present application;

Figure 4 is a schematic diagram of a process association provided by an embodiment of the present application;

Figure 5 is a schematic diagram of a statistical method for process memory usage provided by an embodiment of the present application;

Figure 6 is a schematic flowchart of another application process checking and killing method provided by an embodiment of the present application;

Figure 7 is a schematic flowchart of a method for recovering key components in an application provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a chip system provided by an embodiment of the present application.

Detailed ways

In the description of the embodiments of this application, unless otherwise stated, "/" means or, for example, A/B can mean means A or B; the "and/or" in this article is just a linkage relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, and A and A exist simultaneously. B, there are three situations of B alone.

Hereinafter, the terms “first” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "exemplary" or "such as" is intended to present the concept in a concrete manner.

Embodiments of the present application provide a process checking and killing method for an application (application, APP), which can be applied to an electronic device installed with one or more APPs. Illustratively, the electronic device in the embodiment of the present application may be a mobile phone, a tablet computer, a personal computer (PC), a personal digital assistant (PDA), a smart watch, a netbook, a wearable electronic device, an enhanced Reality technology (augmented reality, AR) equipment, virtual reality (VR) equipment, vehicle-mounted equipment, smart screens, smart cars, smart speakers, robots, etc. This application does not place special restrictions on the specific forms of this electronic equipment.

FIG. 1 shows a schematic structural diagram of an electronic device 100 .

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro 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, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented 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 (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions 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, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and /or universal serial bus (USB) interface, etc. It can be understood that the interface connection relationships between the modules illustrated in the embodiment of the present invention are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the electronic device 100 . While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

A modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110 and may be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). emitting diode (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process the data fed back by the camera 193. Camera 193 is used to capture still images or video. Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy. Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code including instruction. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 .

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. For example, the software system of the electronic device 100 may be the Hongmeng system, Android system, etc. This embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

FIG. 2A is a software structure block diagram of the electronic device 100 according to the embodiment of the present invention.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into five layers. From top to bottom, they are the application layer (referred to as the application layer), the application framework layer (referred to as the framework layer), the Android runtime (Android runtime) and the system library. Hardware Abstraction Layer (HAL) and kernel layer.

(1)Application layer

The application layer can include a series of application packages. As shown in Figure 2A, the application package can include camera, gallery, calendar, calling, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

(2)Frame layer

The framework layer provides application programming interface (API) and programming framework for applications in the application layer. The framework layer includes some predefined functions.

As shown in Figure 2A, the framework layer can include activity manager, window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

Among them, the activity manager is responsible for the startup of all APP processes, the startup of the four major components of the APP (such as activity, service, broadcast receiver, content provider), the interface between APPs and within the APP. switching and the life cycle of various components. A window manager is used to manage window programs. The window manager can obtain the display size, 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 this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed 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 phone manager is used to provide communication functions of the electronic device 100 . For example, call status management (including connected, hung up, etc.). The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc. Notification manager enables The application can 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 download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the electronic device vibrates, the indicator light flashes, etc.

In some embodiments of the present application, the framework layer also includes a component cleaning module. This component cleaning module is used to clean components according to certain strategies. For example, the least recently used (Least Recently Used, LRU) algorithm is used to filter components that are not frequently used recently, and the filtered components are cleaned up. The component cleaning module is also used to clean up the components associated with the killed process after receiving information about the kernel-level killing process. In other embodiments, the component cleaning module is also used to determine whether the component associated with the process to be killed is a critical component to determine whether to clean the component. Among them, key components refer to components that contain key information. The key information includes information that will affect the stability of the system when the target process is running, or affect the user experience. This embodiment will be described in detail below, and will not be described here.

(3)Android Runtime and system libraries

As shown in Figure 2A, Android Runtime includes core libraries and virtual machines. Android runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

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

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc.

Among them, the surface manager is used to manage the display subsystem and provides the integration of 2D and 3D layers for multiple applications. The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing. 2D Graphics Engine is a drawing engine for 2D drawing.

(4)HAL

HAL, used to abstract hardware. HAL hides the hardware interface details of a specific platform and provides a virtual hardware platform for the operating system, making it hardware-independent and portable on multiple platforms. In other words, all hardware-related operations required by the upper layer require calling HAL-related APIs, such as audio and video interfaces, GPS interfaces, call interfaces, Wi-Fi interfaces, and other interfaces.

(5) Kernel layer

The kernel layer is the layer between hardware and software.

The kernel layer includes the kernel allocator, memory statistics module and process killing module. Furthermore, the kernel layer also includes processes/threads, audio and video drivers, GPS drivers, Wi-Fi drivers, etc.

Among them, the kernel allocator can allocate memory to maintain the running status of each process on the electronic device. The memory statistics module is used to count the various types of memory requested by each process. This memory statistics module is used to count power The various types of memory occupied by each process in the sub-device. Among them, the various types of memory occupied by each process can include memory occupied by files, memory occupied by user-mode anonymous pages, memory occupied by streaming media, and memory occupied by the kernel.

As shown in Figure 2B, the memory occupied by the above file types may include the memory occupied by file pages, the memory occupied by core library files, and the memory occupied by cache data. Specifically, the file page may include code files of the application program and resource files (such as icons and pictures) when the application is running. For example, the code files of the application may include the application's configuration files (such as .dex files) and class files (such as .class files). Core library files can include dynamic link libraries (such as .so files, a binary file) that the application needs to access when running. Cached data may include data on file attributes stored in the electronic device for caching purposes. In a specific implementation, the electronic device can use the mmap allocator (more specifically, the file page allocator) between the application layer and the framework layer in Figure 2A to allocate the memory occupied by the file page and the memory occupied by the cache data. The electronic device can use the mmap allocator (more specifically, the core library file allocator) between the framework layer and the Android runtime layer in Figure 2A to allocate the memory occupied by the core library file. In some examples, the core library file allocator can be implemented by encapsulating the file page allocator. The embodiments of this application do not limit the specific implementation of the core library file allocator.

The memory occupied by the above-mentioned user-mode anonymous page can include dynamically allocated memory during the running of the application, and can include memory consumption caused by calling the API of the framework layer and the programming framework. The APIs and programming frameworks of the called framework layer may include: APIs of high-level languages (such as Java language, JavaScript language, TypeScript language), system components of high-level languages, and system frameworks of system languages (such as C++ language, C language). In a specific implementation, the electronic device can use the mmap allocator (more specifically the anonymous page allocator) between the framework layer and the Android runtime in Figure 2A to call high-level language APIs and high-level language system components for the application. Allocate the required memory. The electronic device can use the C++ allocator between the framework layer and the system library in Figure 2A to allocate the memory required for the system framework that the application calls the system language (such as C++ language, C language).

It should be noted that in some examples, in order to save user-mode anonymous page data from occupying memory, the operating system can compress user-mode anonymous page data that is not used frequently. It should be noted that the electronic device specifically triggers the behavior of compressing user-mode anonymous page data by the kernel layer, and stores the compressed data (also called Zram compressed data) in the memory space used to store Zram compressed data. The kernel provides unified management and control of Zram compressed data. That is to say, in a specific implementation, the memory space for storing Zram compressed data can be allocated by the kernel allocator of the kernel layer in Figure 2A.

The memory occupied by the above streaming media includes the memory allocated by the dedicated streaming media memory allocator. Specifically, most applications (such as video applications, music applications, game applications, social applications, etc.) have streaming media playback capabilities. This type of application often requires the computing power of different hardware in the SoC chip in the electronic device. In order to ensure efficient sharing of data between different hardware (such as CPU, DSP, GPU, VPU), the operating system provides a dedicated streaming media memory allocator (such as Android's ION memory allocator). In a specific implementation, the electronic device can use the streaming media memory allocator between the system library and HAL in Figure 2A to allocate memory for these applications to play streaming media. It should be noted that the memory occupied by streaming media can only be actively released by the applicant (that is, the application that applies for streaming media memory), and the kernel cannot uniformly control the memory occupied by streaming media.

The memory occupied by the above kernel can include: memory consumed by kernel operations such as Vmalloc and Slab, memory used for page table conversion (Page Table Entries, PTE), Kernel Stack that maintains application process information, and memory occupied by Zram compressed data. memory, and shared memory (such as Shmem) for efficient communication between multiple processes. In a specific implementation, the electronic device can use the kernel segmentation of the kernel layer in Figure 2A The orchestrator allocates memory occupied by the kernel.

All in all, the above memory statistics module can obtain various types of memory occupied by each process from the mmap allocator, C++ allocator, streaming media memory allocator and kernel allocator. It should be noted that in some other embodiments, the electronic device may also include multiple sub-statistical modules, for example, different sub-statistical modules are respectively provided at mmap allocator, C++ allocator, streaming media memory allocator, etc., for Count the memory allocated by each allocator for the process. Then the sub-statistics module summarizes the statistical data to the memory statistics module of the kernel layer (also called the total statistics module). The statistics module of the kernel layer analyzes the various types of memory of each process to determine the target of killing. process. Or, in other embodiments, the electronic device only sets sub-statistics modules at, for example, mmap allocator, C++ allocator, streaming media memory allocator, kernel allocator, etc., and does not set a total statistics module. Then, the sub-statistical modules directly pass their respective statistical data to the process killing module, and the process killing module analyzes the various types of memory of each process to determine the target process for killing. The embodiments of this application do not specifically limit this.

As shown in Figure 2A, the above-mentioned process killing module is used to detect the triggering events of the process killing process, and select the process to be killed (i.e. the target process) based on the various types of memory occupied by each process detected by the above-mentioned memory statistics module. ), perform scanning and killing on the selected target process, etc.

The technical solutions involved in the following embodiments can be implemented in the electronic device 100 with the above hardware architecture and software architecture.

In one technical solution, the electronic device can use a waterline triggering mechanism based on the amount of remaining memory to kill the process. Specifically, the electronic device can monitor the remaining memory amount of the electronic device. When it is detected that the remaining memory amount is less than or equal to the threshold 1, the electronic device starts the process killing process. Among them, the remaining memory refers to the available memory, which can include the free memory in the system and the memory occupied by files (including the memory occupied by file pages, core library files and cached data). It should be noted that since most file pages, core library files and cache data are backed up in the storage devices of electronic devices (such as Flash devices), during the memory recycling process, the electronic device can directly clean up the memory occupied by this part of the data. , there is no need to first perform some operations that require system overhead (such as backup) on this part of the data and then clean up the memory occupied by this part of the data. In other words, the memory occupied by this part of the data is low-overhead recyclable memory. Therefore, the memory occupied by this part of the data belongs to available memory.

After the electronic device starts the process checking and killing process, the electronic device can determine the target process for checking and killing by combining the usage frequency of the process and the amount of memory occupied by the process. For example, when an electronic device starts the killing process, the electronic device first uses the least recently used (Least Recently Used, LRU) algorithm to filter out processes that are not frequently used as candidate processes, and then selects processes based on the memory usage of each candidate process. Select the candidate process that occupies a large amount of memory as the target process, and then kill the target process to release the memory occupied by the target process.

It should be noted that in the existing technology, a variety of tools have been provided in the Linux kernel to obtain the memory usage of each process. For example, the electronic device can use the top command, the ps command, and other commands, or a combination of any of these commands to obtain the memory usage of each candidate process. It should be noted that when obtaining the memory usage of each process, the existing technology only counts the memory occupied by the process in the user mode (recorded as the first type of memory), but does not count the memory occupied by the process in the kernel state (recorded as the first type of memory). is the second type of memory). Among them, the first type of memory can include memory occupied by files and memory occupied by user-mode anonymous pages. In the embodiment of this application, the memory occupied during the running of the process that is not counted in the prior art is recorded as the second type of memory. The second type of memory can include memory occupied by streaming media and memory occupied by the kernel. It is understandable that the first type of memory can be a process using a memory allocator (such as the mmap allocator), or memory allocated through the framework layer using a memory allocator (such as the C++ allocator). The second type of memory can be memory allocated by the process through the system library using a dedicated streaming allocator, or through the kernel allocator at the kernel level.

It can be understood that since the prior art only counts the first type of memory occupied during the running process of the process, when the electronic device determines the target process based on the occupation of the first type of memory of each candidate process, the electronic device selects the third type of memory. One type of candidate process that occupies a large amount of memory is the target process. Then, after killing the target process, the electronic device will reclaim the first type of memory occupied by the target process. It is understandable that in actual usage scenarios, the proportion of the first type of memory occupied by the process in the whole machine memory may not be high, so the benefit of killing the target process determined based on the first type of memory usage is small. If it is not conducive to maintaining the available memory of the electronic device at a high value, the electronic device may need to frequently trigger process killing behaviors, which may easily cause the system to crash.

To this end, an embodiment of the present application provides a method. When counting the memory occupied during the running of a process, the first type of memory and the second type of memory occupied during the running of the process are also counted. That is, the first type of memory and the second type of memory are counted. The total amount of memory occupied by the second type of memory. Then, when the electronic device performs process killing, it will determine the target process based on the total occupation of the first type of memory and the second type of memory of each candidate process. Moreover, after killing the target processes, the electronic device will reclaim the first type of memory and the second type of memory occupied by these target processes. Since the first type of memory and the second type of memory recovered through this method account for a high proportion of the entire machine memory, it is conducive to maintaining the available memory of the electronic device at a higher value and preventing the electronic device from frequently triggering process checks. Killing behavior is conducive to improving the smoothness and stability of the operation of electronic devices.

The technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

As shown in Figure 3, it is a schematic flow chart of a method for checking and killing application processes provided by the embodiment of the present application. The process includes:

S301. The electronic device runs one or more APPs.

Take the electronic device running APP1 as an example for explanation. When the electronic device runs APP1, APP1 can start multiple processes, such as a foreground process and a background process. Among them, the foreground process can be used to present the user interface of APP1 and interact with the user. In one example, APP1 first starts a foreground process, which can launch one or more background processes. The background processes do not need to interact with the user. The one or more background processes may include a background service process of APP1 or a system service process of the electronic device. Furthermore, this one or more background processes can also start other background processes again. All in all, an APP may start multiple processes, and these processes will apply for corresponding memory and other system resources in the electronic device during operation. Of course, an APP may only start one process, or the APP may only start one process in some scenarios and multiple processes in other scenarios.

S302. The electronic device counts the first type of memory and the second type of memory occupied by each process started by the one or more APPs.

In some embodiments, the electronic device can instrument each memory allocator and count the types of memory requested by each process from each memory allocator, including the first type of memory and the second type of memory. Among them, instrumentation refers to inserting some probes (also called "probes") into the program on the basis of ensuring the original logical integrity of each memory allocator. They are essentially code segments for information collection, which can be assignments. statement or function call to collect coverage information), and through the execution of the probe, the classified memory requested by each process through each memory allocator is collected.

Here we take the second type of memory occupied by statistical processes as an example for explanation. As mentioned above, the process occupies the second Class memory can include memory allocated by streaming allocators (such as the ION memory allocator) and memory allocated by kernel allocators. Among them, the memory allocated by the kernel allocator includes the memory consumption of kernel operations such as Vmalloc and Slab, PTE (Page Table Entries) memory for page table conversion, Kernel Stack for maintaining application process information, and Zram compressed data storage. memory, and shared memory (such as Shmem) for efficient communication between multiple processes.

In a specific implementation, monitoring can be implemented at the EGL Track interface of the streaming media allocator (such as the ION memory allocator) to count the memory allocated by the streaming media allocator to the process. Monitoring can be implemented by instrumenting the kernel zsalloc memory allocation interface to count the memory occupied by Zram compressed data. Monitoring can be implemented by instrumenting the kernel Shmem memory allocation interface to count the shared memory requested by the process. Other allocators in the kernel, such as PTE, Kernel Stack, Slab, Slab Large, Vmalloc, etc., also provide corresponding memory statistics interfaces. They can be installed at the corresponding statistics interfaces to implement monitoring to count various types of memory requested by the process. , I won’t go into details here.

It should be noted that some processes may need to be linked with other processes to jointly complete related tasks. For example, a process started by an APP (such as process 1) may start another or multiple processes (such as process 2). This one or more processes may also apply for memory, such as first-class memory, and/or second-class memory). In the existing technology, if process 2 applies for the first type of memory, the first type of memory applied by process 2 may be counted as the memory occupied by process 2, and will not be counted as the memory occupied by process 1. Then, when it is determined that process 1 is the target process, the memory occupied by process 2 will not be reclaimed when killing process 1. It is understandable that the memory requested by process 2 is to support the operation of process 1. If process 1 is killed, the memory requested by process 2 will have no effect, which causes a waste of memory. Or, if process 2 applies for the second type of memory, the existing technology cannot count the second type of memory applied by process 2, which will still cause the problem of low profits after the process is killed.

For this reason, in other embodiments of the present application, when counting the memory of each process, the electronic device will calculate the memory applied for by each process based on the linkage relationship between the processes (also known as the pull-up relationship, calling relationship, etc.) Assigned to the source process. In this way, when the subsequent electronic device selects the target process to be checked and killed, it can accurately determine the target process that occupies the largest amount of the first type of memory and the second type of memory of the system, and can recover more when checking and killing the target process. The first type of memory and the second type of memory, thereby increasing the benefits of process killing and improving the smoothness and stability of the system.

In specific implementation, since the linkage relationship between processes requires inter-process communication services in the system (such as Binder, Socket, and Signal), electronic devices can collect statistics on each process by monitoring the inter-process communication services. Linkage relationship. In some examples, the electronic device can maintain a linked list of linkage relationships between processes (Figure 4 shows an example of a linked list of linkage relationships between processes) to collect statistics on linkage relationships between different processes. Among them, the electronic equipment can be counted using methods such as red-black trees or hash tables. Then, based on the linkage relationship of each process, the memory requested by each process is finally counted to the source process. Among them, the source process refers to the first caller. For example, process 1 calls process 2, and process 2 calls process 3. Then, the source process of process 2 and process 3 is process 1.

As shown in Figure 5, APP1 is taken as an example to illustrate the linkage relationship between processes of APP1 and the method of counting memory. When running APP1, the main process of APP1 (such as the foreground process) will be started. The main process of APP1 may call the background services of the framework layer, and/or the system library and runtime layer (each service will correspond to a process). For example, the main process calls audio and video services, and the audio and video services pass the graphical allocator (Graghic Allocator). ) applies for streaming media memory (such as ION memory). Then, the electronic device establishes the main process of APP1 (or APP1) The linkage relationship with the audio and video service counts the memory requested by the audio and video service to the main process of APP1 (or APP1). Similarly, when the APP1 main process calls the image rendering service, the image rendering service applies for streaming media memory (such as ION memory) through the graphics allocator (Graghic Allocator). Then, the electronic device establishes a linkage relationship between the main process of APP1 (or APP1) and the image rendering service, and counts the memory requested by the image rendering service to the main process of APP1 (or APP1).

In some scenarios, when the system's memory is tight, the APP1 main process may also call the kernel layer's memory management service to compress the user-mode anonymous page data and apply for memory to store the compressed data (for example, to store Zram compression data memory). Then, the electronic device can count the memory applied for this time by the memory management service to the APP1 main process (or APP1). Similarly, the APP1 main process may also call the inter-process communication (such as Binder) module of the kernel layer to apply for shared memory (such as Ashmem). Then, the electronic device counts the shared memory applied for this time by the inter-process communication module to the main process of APP1 (or APP1). Similarly, the main process of APP1 calls the memory business module of the kernel layer to apply for other kernel memory (such as page table PT, Stack, Slab, Vmalloc). Then, the electronic device counts the various kernel memories applied for this time by the memory business module to the main process of APP1 (or APP1).

It should be noted that the linkage relationship between different processes maintained by the electronic device here is used here to count the memory requested by each called process to the source process. When subsequent electronic devices perform process killing, in addition to killing the selected In addition to the target process, you can also kill processes that are linked to the target process to reclaim more memory and improve the operating efficiency of the system. This will be explained in detail later.

S303. When it is detected that the memory of the electronic device meets the preset conditions, the electronic device determines the target process from the processes started by the one or more APPs.

Among them, the memory of the electronic device meets the preset conditions, which is the trigger condition for the electronic device to execute process killing. For example, the memory of the electronic device that meets the preset conditions includes: the remaining memory amount of the electronic device is less than or equal to the threshold 1; or the blocking duration of the process in the electronic device due to untimely memory allocation is greater than or equal to the threshold 2; or the electronic device The total occupancy of the second type of memory is greater than or equal to any of threshold 3.

In some embodiments, the electronic device may use a waterline triggering mechanism based on the amount of remaining memory to kill processes. Specifically, the electronic device can monitor the amount of remaining memory of the electronic device, where the remaining memory refers to available memory, which can include free memory in the system, as well as memory occupied by file pages, core library files, and cached data. When it is detected that the remaining memory amount is less than or equal to the threshold 1, the electronic device starts the process killing process.

After the electronic device starts the process checking and killing process, the electronic device can determine the target process for checking and killing by combining the usage frequency of the process and the amount of memory occupied by the process. For example, when the electronic device starts the killing process, the electronic device first uses, for example, the LRU algorithm to filter out processes that are not frequently used as candidate processes, and then selects the candidate process with a larger memory footprint based on the memory usage of each candidate process. As the target process, then kill the target process to release the memory occupied by the target process.

It should be noted that the memory usage of each candidate process includes the first type of memory usage and the second type of memory usage. That is to say, the electronic device is based on the first type of memory and the second type of memory occupied by each candidate process. The total usage is used to determine the target process.

Optionally, in a scenario where there is a linkage between multiple processes running on an electronic device, the memory usage of each candidate process may also include the memory requested by other processes called by each candidate process (also including the first type of memory and Type II memory). Furthermore, the electronic device can also be configured according to the target process and the electronic device maintenance Use the linkage relationship between different processes protected to determine other processes called by the target process, and determine that these other processes are also processes that need to be killed, that is, they are also target processes. It is understandable that after the target process is checked and killed, if other processes called by the target process are only called by the target process, then these other processes can also be checked and killed, and the memory occupied by these other processes can also be recycled. This will help further improve memory utilization and improve the system's operating speed. Of course, if other processes called by the target process are also called by other non-target processes, these other processes cannot be killed to ensure the normal operation of other non-target processes.

For example, please continue to refer to Figure 5. If the main process of APP1 is determined to be the target process, in addition to killing the main process of APP1 and reclaiming the memory requested by the main process of APP1, if the audio and video services and image rendering services called by APP1 have not been If the process calls of other applications, it can also be determined that the audio and video service and image rendering service are also target processes. Then, the electronic device also kills the audio and video services and image rendering services, and recovers the streaming media memory (such as ION memory) occupied by the audio and video services and image rendering services. It is understandable that streaming media usually takes up a large amount of memory. Then, the audio and video killing service and image rendering service will recycle this part of the streaming media memory, which is more conducive to increasing the benefits of process killing and maintaining the stability and smoothness of system operation.

In other embodiments, the electronic device may also use a triggering mechanism based on Pressure Stall Information (PSI) to kill the process. Specifically, the electronic device can monitor the blocking time caused by untimely memory allocation when each process on the electronic device is running, that is, the time the process waits for memory allocation. When it is detected that the blocking time of the process is greater than or equal to the threshold 2, the process killing process is started. It should be noted that the difference between this embodiment and the previous embodiment is that the triggering conditions for initiating the process checking and killing process are different. The specific method for the electronic device to perform process checking and killing is the same as the previous embodiment, and will not be described again here.

In some embodiments, the electronic device can also use a waterline triggering mechanism based on the second type of memory usage to kill the process. Specifically, the electronic device can monitor the total occupied amount of the second type of memory in the electronic device. When it is detected that the total occupied amount of the second type of memory is greater than or equal to the threshold 3, the electronic device starts the process killing process. It should be noted that the difference between this embodiment and the above-mentioned embodiment is that the triggering conditions for initiating the process checking and killing process are different. The specific method of executing process checking and killing by the electronic device is the same as that in the above-mentioned embodiment, and will not be described again here.

In addition, this embodiment provides a method for monitoring the memory usage of an electronic device from the perspective of monitoring the second type of memory usage. In the actual use of electronic devices, the second type of memory occupancy is usually large, which is one of the main reasons for the memory shortage of electronic devices. Therefore, the startup process killing process is determined from the perspective of monitoring the second type of memory occupancy. Being able to more accurately monitor the memory usage of electronic devices is more conducive to fundamentally solving the problems of high memory pressure and slow system operation caused by high second-type memory usage of electronic devices. In addition, since this embodiment realizes the function of recycling the second type of memory, it effectively reduces the occupation of the second type of memory, which helps the system's available memory to stay at a higher threshold for a long time, ensuring the stability and smoothness of the system operation. .

It should also be noted that the methods provided by the above embodiments can be used in combination if the solutions themselves are not inconsistent, or the methods provided by the above embodiments can be used in combination with existing technologies. For example, the electronic device may simultaneously adopt a watermark triggering mechanism based on the amount of remaining memory and a watermark triggering mechanism based on the second type of memory usage. When it is detected that the remaining memory of the electronic device is less than or equal to the threshold 1, the process of killing the process is started. The process checking and killing method here may adopt existing technology, or may adopt the process checking and killing method provided by the embodiments of this application. When it is detected that the occupation of the second type of memory of the electronic device is greater than or equal to the threshold 3, the process of killing the process is also started. It is understandable that since the electronic device adopts a trigger mechanism based on the second-type memory usage waterline, and the electronic device recycles more second-class memory when executing the scanning and killing process of the process, it is conducive to the remaining memory of the electronic device. Inside If the inventory is at a high threshold for a long time, it also reduces the frequency of process killing triggered by electronic devices using a trigger mechanism based on the remaining memory waterline of the electronic device, and reduces the system consumption of electronic devices executing the process killing process. Resources, such as CPU resources, memory resources, etc.

S304. Check and kill the target process of the electronic device.

The electronic device scans and kills the determined target process, and reclaims the first type of memory and the second type of memory occupied by the target process. More specifically, after the kernel layer of the electronic device kills the target process, it notifies the upper layer that the target process has been killed. After receiving the notification information, the framework layer further cleans up the components associated with the target process and further releases the memory occupied by the components.

In summary, since the first type of memory and the second type of memory recovered through this method account for a high proportion of the entire machine's memory, it is conducive to maintaining the available memory of the electronic device at a higher value, which is conducive to improving the operation of the electronic device. fluency and stability.

In addition, because the process checking and killing method provided by the embodiment of the present application has greater benefits, it is conducive to maintaining the available memory of the electronic device at a higher value, reducing the frequency of the electronic device executing the process checking and killing process, and reducing the cost of the process. The system resources consumed by electronic devices when executing process killing processes, such as CPU resources, memory resources, etc.

In some other embodiments, when considering the above method when selecting a target process, some processes with higher priority or system level may be determined as the target process. In order to ensure the stability of the system operation or ensure the user experience, during the process of killing the target process, the key components in the target process are identified (that is, the information in the key components affects the stability of the system or the user experience) , and preserve key components in the target process. Later, when the target process is restarted (or the APP corresponding to the target process is restarted), the retained key components can be directly used to restore the target process to ensure the stability of the system operation or the user experience.

As shown in Figure 6, it is a schematic flowchart of another method for detecting and killing an application process provided by an embodiment of the present application. The process includes:

S601. Monitor whether the occupancy of the second type of memory of the electronic device is greater than or equal to threshold 3. If it is detected that the occupancy of the second type of memory of the electronic device is greater than or equal to threshold 3, step S602 is executed.

It can be understood that here, the occupancy of the second type of memory of the electronic device is greater than or equal to the threshold 3 as the trigger condition for the electronic device to execute process killing. In some other embodiments, the electronic device may also adopt Other triggering conditions will not be described here.

In a specific implementation, the kernel layer (for example, more specifically, the memory statistics module of the kernel layer) monitors whether the occupation amount of the second type of memory of the electronic device is greater than or equal to the threshold 3.

S602. Count the memory usage of each process. The memory usage of each process includes the total usage of the first type of memory and the second type of memory.

It can be understood that in some other embodiments, the electronic device may also start to count the memory usage of each process in real time while executing step S601 or before executing step S601. In a specific implementation, the kernel layer (for example, more specifically, the memory statistics module of the kernel layer) is used to count the memory usage of each process.

For other contents of this step, please refer to the relevant contents in the above-mentioned step S302, which will not be described again here.

S603. Select the target process.

In some embodiments, the electronic device may determine the target process for scanning and killing by combining the usage frequency of the process and the amount of memory occupied by the process. For the specific method of selecting the target process, please refer to the relevant content in the above step S302, which will not be described again here. In a specific implementation, the kernel layer (for example, more specifically, the inner layer of the kernel layer The memory statistics module) is used to select the target process based on the statistical memory usage of each process.

S604. Check and kill the target process.

In a specific implementation, the kernel layer (for example, more specifically, the process killing module of the kernel layer) is used to kill the target process.

S605. Determine whether the component associated with the target process is a critical component. If it is a key component, perform step S606. If it is not a critical component, perform step S607.

Among them, key components refer to components that contain key information. The key information includes information that will affect the stability of the system when the target process is running, or affect the user experience. It is understandable that some temporary data while the target process is running will be stored in the component. If you clean up the components associated with the target process directly after killing the target process, this part of the temporary data will be lost. If the temporary data contains critical information, it will inevitably affect the restart of the target process, the stability of the target process, or the user experience. For example, key components may include information about some permanent functions when the system is running, such as information about the electronic device's negative screen, magazine lock screen information, information displayed on the active screen, weather widget information, etc. For another example, the key component may include the reading progress information of the electronic document, and the reading progress information of the electronic document will affect the user's experience when reading the electronic document.

Therefore, when the electronic device cleans the components associated with the target process, it will first determine whether the components associated with the target process contain key components. For key components, retain the information of the key components, or retain the key information in the key components, that is, perform step S606. For non-critical components, clean up non-associated components, that is, perform step S607.

In a specific implementation, after the kernel layer (for example, the process killing module of the kernel layer) kills the target process, it notifies the upper layer that the target process has been killed. The framework layer (for example, more specifically, the component cleaning module of the framework layer) determines whether the components associated with the target process are critical components, and further retains the critical components and cleans the non-critical components.

S606. Save the information of key components.

Before cleaning up the components associated with the target process, decouple the key components from the target process and modify the running status of the key components to save the information of the key components.

In some other embodiments, the electronic device can also modify the life cycle of key components to retain information about key components.

S607. Clean up non-critical components.

As a result, the information of key components associated with the target process is retained, so that the electronic device can subsequently restore the information of key components, maintain the stability of system operation, and provide user experience.

As shown in Figure 7, it is a schematic flowchart of a method for restoring a target process provided by an embodiment of the present application. The process includes:

S701. Call the component.

For example, after the APP is restarted, the main process of the APP (or other processes, such as other processes called by the main process) can call components in the framework layer to implement corresponding functions. Or, the APP does not exit, and the APP's main process (or other processes, such as other processes called by the main process) needs to call the components in the framework layer again to implement the corresponding functions.

S702. Determine whether the called component is a recoverable key component. If yes, execute step S703; if not, execute step S706.

For example, the main process of the APP (or other processes, such as other processes called by the main process) can query the component records to determine whether the component to be called is a recoverable key component. That is, whether the electronic device saves information about the component to be called. If it is determined that the component to be called is a recoverable key component, the component can be recovered using the information of the key component retained by the electronic device, that is, steps S703 to S705 are performed. If it is determined that the component to be called is not a recoverable critical component, the system's native process is adopted, that is, steps S706 to S709 are executed.

S703. Create a process.

Since the component needs to rely on a process to run, the electronic device creates a new process for running the component.

S704. Establish an association between processes and components.

S705. Run the component.

This process ends.

S706. Determine whether a component needs to be created. If not, execute step S707. If so, execute step S708,

For example, before calling, query whether the electronic device runs the component. If the electronic device does not run the component, the component needs to be created, that is, step S707 is performed. If the electronic device runs the component, there is no need to create the component again, and step S708 is executed.

S707. Determine whether a new process needs to be created. If so, execute step S703.

S708. Create a component.

S709. Determine whether there is an existing process that can take over the created component. If yes, execute step S704. If not, execute step S703.

An embodiment of the present application also provides a chip system. As shown in FIG. 8 , the chip system includes at least one processor 1101 and at least one interface circuit 1102 . The processor 1101 and the interface circuit 1102 may be interconnected by wires. For example, interface circuitry 1102 may be used to receive signals from other devices, such as the memory of electronic device 100 . As another example, interface circuit 1102 may be used to send signals to other devices (eg, processor 1101). For example, the interface circuit 1102 can read instructions stored in the memory and send the instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can be caused to perform various steps performed by the electronic device 100 (such as a mobile phone) in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of this application.

An embodiment of the present application also provides a device, which is included in an electronic device and has the function of realizing the behavior of the electronic device in any of the methods in the above embodiments. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above functions. For example, detection module or unit, statistical module or unit, determination module or unit, and killing module or unit, etc.

Embodiments of the present application also provide a computer storage medium that includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to perform any of the methods in the above embodiments.

Embodiments of the present application also provide a computer program product. When the computer program product is run on a computer, it causes the computer to perform any of the methods in the above embodiments.

It can be understood that, in order to implement the above functions, the above-mentioned electronic devices include hardware structures and/or software modules corresponding to each function. Persons skilled in the art should easily realize that, in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or by computer software driving the hardware? Depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered to be beyond the scope of the embodiments of the present invention.

Embodiments of the present application can divide the above-mentioned electronic equipment into functional modules according to the above-mentioned method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present invention is schematic and is only a logical function division. In actual implementation, there may be other division methods.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

Each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage device. The medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for checking and killing application processes, characterized in that the method includes:

The electronic device runs one or more applications;

The electronic device counts the first type of memory and the second type of memory occupied by each process started by the one or more APPs, wherein the first type of memory includes the memory occupied by file pages, the memory occupied by core library files, and the memory occupied by cached data. Memory, and one or more items in the memory occupied by user-mode anonymous pages; the second type of memory includes one or more items in the memory occupied by streaming media and the memory occupied by the kernel;

When it is detected that the memory of the electronic device meets the preset conditions, the electronic device starts from the one or more APPs according to the first type of memory and the second type of memory occupied by the respective processes. Determine the target process in the process;

The electronic device checks and kills the target process.
The method according to claim 1, characterized in that:

The memory of the electronic device meeting the preset conditions includes: the remaining memory amount of the electronic device is less than or equal to the first threshold, and the blocking duration of the process in the electronic device due to untimely memory allocation is greater than or equal to the second threshold, so The total occupied amount of the second type of memory in the electronic device is greater than or equal to any one of the third thresholds.
The method according to claim 1 or 2, characterized in that,

The first type of memory and the second type of memory occupied by the first process include the first type of memory and/or the second type of memory occupied by the second process called by the first process; wherein the first process is the one or any one of the processes started by multiple APPs, and the second process is not called by other processes except the first process.
The method according to claim 3, characterized in that:

The electronic device determines a target process from the processes started by the one or more APPs according to the first type of memory and the second type of memory occupied by each process, including: the electronic device determines the After the first process is the target process, it is determined that the second process is also the target process.
The method according to any one of claims 1 to 4, characterized in that, after the electronic device kills the target process, the method further includes:

The electronic device determines whether the first component associated with the target process is a key component; wherein the key component is a component that contains key information, and the key information includes whether the target process will affect system operation stability or affect system operation stability when running. Information about the user’s experience;

If it is determined that the first component is the critical component, the electronic device retains the information of the first component; if it is determined that the first component is not the critical component, the electronic device clears the third component. Information about a component.
The method according to claim 5, wherein the key information includes one of negative screen information, magazine lock screen information, interest screen display information, weather widget information, and electronic document reading progress information. or multiple items.
The method according to claim 5 or 6, characterized in that, after the electronic device kills the target process and after the electronic device retains the information of the first component, the method further includes:

The electronic device calls the first component;

After querying that the electronic device retains information about the first component, the electronic device starts a third process;

The electronic device establishes the third process and the first group according to the retained information of the first component. Piece relationships.
An electronic device, characterized by comprising: a processor and a memory, the memory being coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, the processor from The computer instructions are read from the memory to cause the electronic device to execute the process checking and killing method of an application program according to any one of claims 1-7.
A computer-readable storage medium, characterized in that it includes computer instructions that, when the computer instructions are run on an electronic device, cause the electronic device to execute the application program according to any one of claims 1-7. Process killing method.
A chip system, characterized in that it includes one or more processors. When the one or more processors execute instructions, the one or more processors execute the method according to any one of claims 1-7. The process killing method of the application mentioned above.
A computer program product, characterized in that, when the computer program product is run on an electronic device, it causes the electronic device to execute the process checking and killing method of an application program according to any one of claims 1-7.