Process control method, computer equipment and computer readable storage medium

Abstract

The embodiment of the invention relates to the technical field of computers, and discloses a process control method, computer equipment and a computer readable storage medium. The process control method comprises the steps that a keep-alive list is provided, and key process information needing to be kept alive is stored in the keep-alive list; continuously monitoring a signal sending function in the kernel through the kernel probe, wherein the signal sending function is at least used for being called by the searching and killing initiating subject to send a searching and killing signal to a target process to be searched and killed; when a preset keep-alive condition is met at present, the kernel probe carries out signal processing on the signal sending function so that the target process to be searched and killed at present can keep alive; wherein the preset keep-alive condition comprises that a signal currently sent by the signal sending function is a searching and killing signal, and the current target process to be searched and killed exists in a keep-alive list. According to the embodiment of the invention, the keep-alive reliability can be effectively improved, the service continuity and the user experience can be guaranteed, the native stability of the system can be maintained, the universality is high, and the transplantation is convenient.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a process control method, a computer device, and a computer-readable storage medium. Background Technology

[0002] The inventors discovered that existing process keep-alive solutions, such as dual-process mutual monitoring, rely on application-layer logic (i.e., process management logic running in user space), which at least suffers from poor reliability.

[0003] This is because existing keep-alive solutions operate in user mode with lower privileges and are subject to system resource scheduling limitations. When the system triggers scenarios such as low memory reclamation or memory overflow, the processes and communication resources (such as inter-process communication channels) on which the application layer keeps-alive depends may be prioritized for killing or reclamation, causing the keep-alive logic to fail directly. For example, in a dual-process mutual monitoring solution, if both processes are killed almost simultaneously due to low memory, there is not enough time to monitor each other and restart the other.

[0004] Therefore, improvements to existing technologies are necessary.

[0005] The above information is provided as background information only to help understand the embodiments of this application, and does not determine or acknowledge whether any of the above content can be used as prior art relative to the embodiments of this application. Summary of the Invention

[0006] This application provides a process control method, a computer device, and a computer-readable storage medium to solve the problem of poor reliability in existing process keep-alive schemes.

[0007] To achieve the above objectives, the embodiments of this application provide the following technical solutions:

[0008] In a first aspect, embodiments of this application provide a process control method, including:

[0009] Provide a keep-alive list, which stores information about critical processes that need to be kept alive;

[0010] The kernel probe continuously monitors the signal sending function in the kernel. The signal sending function is at least used by the killing initiator to send a killing signal to the target process to be killed.

[0011] When the kernel probe detects that the preset keep-alive conditions are met, it performs signal processing on the signal sending function so that the target process to be killed can be kept alive and not killed.

[0012] The preset keep-alive conditions include: the signal currently sent by the signal sending function is a kill signal, and the target process to be killed exists in the keep-alive list.

[0013] Optionally, the preset keep-alive condition also includes: the current detection and killing initiator is a preset target entity.

[0014] Optionally, the initiating entity for the detection includes low memory killer, memory overflow killer, activity management service and / or kill command tool; the preset target entity includes low memory killer.

[0015] Optionally, the detection signal includes a termination signal;

[0016] The kernel probe performs signal processing on the signal sending function to keep the target process alive and prevent it from being killed, including:

[0017] Before the signal sending function is sent to the target process to be killed, the termination signal in the signal sending function is replaced with a continuation signal; wherein the termination signal is used to instruct the target process to terminate, and the continuation signal is used to instruct the target process to continue running.

[0018] Optionally, the key processes are configured by the application layer, preset by the system, and / or dynamically identified.

[0019] Optionally, the key processes include: music process, system push service process, location service process, and / or background download process.

[0020] Optional, also includes:

[0021] A detection and removal call interface is provided, which is used to provide a preset upper-layer application or service so that it can directly call the signal sending function.

[0022] When the detection and removal mechanism is triggered, the preset upper-layer application or service determines the target process to be detected and removed, and directly calls the signal sending function through the detection and removal call interface to send a detection and removal signal to the target process.

[0023] Optionally, the timing of triggering the detection and removal mechanism includes: when the system resource occupancy rate continuously exceeds a preset occupancy threshold, or when a process is detected to be unresponsive for a duration exceeding a preset duration threshold, or when the user actively calls the detection and removal interface.

[0024] Secondly, embodiments of this application provide a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor, when executing the computer program, implements the process control method as described in any of the above.

[0025] Thirdly, embodiments of this application provide a computer-readable storage medium having computer-executable instructions stored thereon, which are executed by a computer processor to implement the process control method as described in any of the preceding claims.

[0026] Compared with the prior art, the embodiments of this application have the following beneficial effects:

[0027] 1) Effectively improves keep-alive reliability: Compared with application-layer keep-alive solutions (such as dual-process monitoring) which are prone to failure due to user-mode resource reclamation or permission restrictions, the embodiments of this application are based on kernel implementation. Even if the critical process is in a low memory or memory overflow scenario, it can still avoid being killed from the root by handling the signal sending function.

[0028] 2) Ensures business continuity and user experience: By precisely protecting critical processes that are essential to user experience or system functionality, it avoids business interruptions, data loss, and user lag caused by process termination. In scenarios with limited system resources such as low memory, it ensures the continuous operation of critical business processes while releasing resources by appropriately terminating abnormal processes, achieving a balance between system performance and user experience.

[0029] 3) Maintains native system stability with low overhead: This application's embodiment employs a kernel probe dynamic interception mode, requiring no modification to the kernel's native source code or recompilation of the kernel. It only loads and executes through dynamic kernel modules, completely unaffecting the system's native signal processing logic and resource scheduling mechanism. Furthermore, the interaction between the kernel probe and the signal sending function is completed instantaneously before signal delivery, resulting in negligible CPU and memory usage. This achieves keep-alive functionality without impacting the system's basic operational stability, making it compatible with various devices.

[0030] 4) High versatility, easy portability, and low adaptation cost: This application's embodiments rely on the kernel's native signal sending functions and kernel probes. The functionality and calling logic of both remain consistent across different kernel versions, without depending on application-layer specific interfaces or permission mechanisms. Compared to existing application-layer keep-alive solutions that require customized development of adaptation logic for different systems and business scenarios, this solution only requires configuring a keep-alive list for rapid deployment. No additional modifications to the core logic are needed, and it can be directly ported to various devices, significantly reducing cross-device and cross-system adaptation costs.

[0031] The embodiments of this application have other features and advantages that will be apparent from or will be set forth in detail in the accompanying drawings and following detailed description, which together serve to explain the particular principles of the embodiments of this application. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart of the process control method provided in the embodiments of this application;

[0034] Figure 2 This is a schematic diagram of the process control method provided in the embodiments of this application. Detailed Implementation

[0035] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of the embodiments of this application.

[0036] Existing process management solutions often suffer from poor reliability due to their reliance on application-layer logic. To overcome this deficiency, this application provides a process management method based on system kernel signal processing. By using a kernel probe (kprobe) to intercept signal sending functions, the method achieves process keep-alive, effectively solving the problems of insufficient stability, high implementation complexity, and high adaptation costs caused by implementation based on upper layers.

[0037] Please refer to Figure 1 This application provides a process control method, specifically including:

[0038] S1. Provide a keep-alive list, which stores information about critical processes that need to be kept alive.

[0039] The keep-alive list is used to store the unique identifiers of each critical process, allowing subsequent kernel probes to quickly match them.

[0040] Critical processes refer to processes that are essential to user experience or system functionality and need to be avoided from being terminated. These can be foreground or background processes, with no specific restrictions. For example, a background music playback process. In practical applications, terminating this process would severely impact user experience; however, this process continuously consumes audio hardware and memory resources. In low-memory scenarios, low-memory killers will prioritize terminating such "resource-consuming but non-critical" processes to release memory. In this case, the background music playback process can be identified as a critical process, and its identification information can be stored in a keep-alive list so that it can be kept alive in low-memory scenarios without being terminated, thus improving the user experience.

[0041] S2. Continuously monitor the signal sending function in the kernel through a kernel probe. The signal sending function is at least used by the entity initiating the kill to send a kill signal to the target process to be killed.

[0042] It needs to be explained that the kernel is the core component of the operating system, managing system resources (CPU, memory, processes, etc.), and serving as an intermediary layer between the application layer and the hardware layer.

[0043] Signal sending functions are kernel-level functions natively included in the Linux / Android operating system kernel. They are used to pass system signals (such as SIGKILL and SIGCONT signals) to the target process and are core kernel functions for process state switching. Signal sending functions are the mandatory channel through which all signals sent by the killer initiator must be executed; that is, all signals sent by the killer initiator (such as SIGKILL and SIGCONT signals) must be executed through the kernel's signal sending functions.

[0044] Kernel probes are lightweight kernel debugging / enhancement tools that run in kernel mode. They have the highest system privileges, are not subject to user-mode resource scheduling restrictions, and are not constrained by any application-layer logic. They can intercept all kernel-level function calls.

[0045] S3. When the preset keep-alive conditions are detected, the kernel probe performs signal processing on the signal sending function so that the target process to be killed can be kept alive instead of being killed. The preset keep-alive conditions include: the signal sent by the signal sending function is a kill signal, and the target process to be killed exists in the keep-alive list.

[0046] Based on this, the embodiments of this application monitor and process the signal sending functions in the kernel using kernel probes, which can accurately intercept the kill signals sent by the kill initiator to the critical process, thereby keeping the critical process alive, and has the following effects:

[0047] This application effectively improves keep-alive reliability: Relying on the unique channel characteristic of the kernel probe running in kernel mode and the signal sending function, it can accurately intercept all kill signals sent by the initiating entity. Compared to application-layer keep-alive solutions (such as dual-process monitoring) which are prone to failure due to user-mode resource reclamation or permission restrictions, this application is implemented in the kernel. Even in scenarios with low memory or memory overflow, critical processes can be prevented from being killed at the source by handling the signal sending function.

[0048] It ensures business continuity and user experience by precisely protecting critical processes essential to user experience or system functionality (such as background music playback, USB data transfer, and core system services). This prevents business interruptions (e.g., data transfer failures, service pauses), data loss (e.g., unsaved operation logs), and user lag (e.g., frequent process restarts) caused by process termination. In scenarios with limited system resources, such as low memory, it ensures the continuous operation of critical business processes while releasing resources by appropriately terminating abnormal processes, achieving a balance between system performance and user experience.

[0049] It maintains the system's native stability with low overhead: This application's embodiment adopts a kernel probe dynamic interception mode, which does not require modification of the kernel's native source code, but only loads and executes through kernel dynamic modules, without affecting the system's native signal processing logic and resource scheduling mechanism. Moreover, the interaction between the kernel probe and the signal sending function is completed only momentarily before the signal is delivered, with negligible impact on the system's CPU and memory usage. It achieves both keep-alive functionality and does not affect the system's basic operational stability, making it compatible with devices of various Linux / Android kernel versions.

[0050] High versatility, easy portability, and low adaptation cost: This application's embodiments rely on the kernel's native signal sending functions and kernel probes. Both maintain consistent functionality and calling logic across various Linux / Android kernel versions, without depending on application-layer specific interfaces or permission mechanisms. Compared to existing application-layer keep-alive solutions that require customized development of adaptation logic for different systems and business scenarios, this solution only requires configuring a keep-alive list for rapid deployment. No additional modifications to the core logic are needed, and it can be directly ported to various electronic devices running Linux / Android kernels, such as mobile phones, tablets, and POS machines, significantly reducing cross-device and cross-system adaptation costs.

[0051] The term "kill initiator" refers to all entities capable of proactively initiating process kill actions and sending kill signals to the target process through kernel signal sending functions. In one optional implementation, the kill initiator may specifically include Low Memory Killer (lmkd), Out Of Memory Killer (OOM Killer), kill command tools, and AMS (Activity Manager Service), etc.

[0052] Low Memory Killer is a kernel-mode daemon natively included in the Linux / Android kernel. Running in kernel mode, it has the highest system privileges and is the most frequently triggered and core component in regular system scans. When the available physical memory of an electronic device falls below a kernel-preset threshold (e.g., 5%-10% of total memory), and the system is in a low-memory scenario rather than memory exhaustion, Low Memory Killer is automatically triggered. After triggering, Low Memory Killer sorts processes according to their priority (background / foreground processes, resource usage type), prioritizing background processes that consume system resources but have no user interaction as targets for elimination.

[0053] The Memory Overflow Killer is a native kernel-mode emergency self-rescue component in the Linux / Android kernel. Running in kernel mode with the highest system privileges, it is the main body that initiates the detection and elimination of memory overflow scenarios. When the physical and virtual memory of an electronic device is completely exhausted, and the kernel cannot satisfy the memory requests of any process, the system is in an extreme scenario of memory overflow (memory exhaustion), and the Memory Overflow Killer will be triggered immediately. After being triggered, the Memory Overflow Killer calculates the memory usage weight of all processes in the system and prioritizes eliminating processes with the highest single-process memory usage that are not essential to the core functions of the system.

[0054] The `kill` command tool is a user-space signal sending tool in Linux / Android systems. It is primarily triggered by developers actively entering commands in the terminal, or indirectly by application-layer scripts or third-party management tools calling the `kill` system call. It has no automatic triggering logic; all killing actions originate from the developer's intentional actions. Furthermore, AMS is a core service component that allows users to forcibly stop apps through system settings and other methods.

[0055] In an optional implementation, the preset keep-alive condition in step S3 further includes: the current killer initiator is a preset target entity. In this embodiment, the keep-alive operation of the signal processing is only executed when the kernel probe detects that the signal sent by the signal sending function is a killer signal, the target process to be killed exists in the keep-alive list, and the initiator of this signal is a preset target entity; if any condition is not met, the kernel's native signal logic is directly allowed.

[0056] Thus, by adding the determination condition for the subject of the kill in this embodiment of the application, the kill behavior of the preset target subject can be kept alive only, while the kill behavior of other subjects is not interfered with. This allows the keep-alive logic of this solution to have boundaries and rationality, and will not cause risks such as abnormal processes not being able to be cleaned up or system resources being exhausted due to excessive keep-alive.

[0057] Furthermore, and exemplaryly, the preset target entity includes the low memory killer. In this case, the embodiments of this application only intervene in the low memory killer entity, without interfering with the detection logic of other entities, thus simultaneously achieving the goals of keeping critical processes alive, ensuring system stability, and respecting user intent.

[0058] This is because the failure of existing application-layer keep-alive solutions (such as dual-process monitoring) is largely due to the killing behavior of low-memory killers. Low-memory killers are the most frequently triggered killers in the system. In daily use of mobile devices such as phones and tablets, low-memory scenarios are common (e.g., multiple applications running in the background, large-memory applications starting up). Low-memory killers indiscriminately kill critical background processes (e.g., background music playback, USB data transfer, location service processes). These processes are crucial to user experience, but due to their lack of user interaction and resource consumption, they become the priority targets of low-memory killers, and the scenarios where users most notice the killing of these processes. This application's embodiment uses the low-memory killer as the core monitoring object, accurately intercepting its killing signals and replacing them, fundamentally solving the core pain point of critical processes being killed in common low-memory scenarios.

[0059] As for the memory overflow killer, it triggers an extreme scenario of complete memory exhaustion. Its killing behavior is the system's ultimate self-rescue. Intervening in its keep-alive action would prevent the kernel from releasing memory, ultimately leading to serious risks such as system crashes and freezes. Therefore, this embodiment respects the kernel's native self-rescue logic and does not intervene. Regarding the kill command tool, its killing behavior is a user's autonomous operation. Intervening in its keep-alive action would prevent the user from manually terminating processes in the keep-alive list, violating the user's operational intentions and preventing the cleanup of abnormal critical processes, leading to excessive resource consumption. Therefore, this embodiment allows its signal to be enabled to balance user autonomy.

[0060] Furthermore, in an alternative implementation, the kill signal may specifically include a SIGKILL signal.

[0061] Based on this, step S3, where the kernel probe performs signal processing on the signal sending function to keep the target process alive and prevent it from being killed, may include:

[0062] Before the signal sending function is sent to the target process to be killed, the SIGKILL signal in the signal sending function is replaced with the SIGCONT signal; the SIGKILL signal is used to instruct the target process to terminate, and the SIGCONT signal is used to instruct the target process to continue running.

[0063] It should be explained that the SIGKILL signal is a forced termination signal in Linux systems that cannot be ignored or caught by a process; a process must exit when it receives this signal. The SIGCONT signal is used in Linux systems to resume the execution of a suspended process. This embodiment replaces the SIGKILL signal with the SIGCONT signal, thus eliminating the forced termination signal and allowing the process to continue running without disrupting the system's operational logic.

[0064] The key processes in the embodiments of this application can be configured and determined in the following ways:

[0065] System default configuration: This refers to the system vendor's pre-entry of core processes—essential for the stable operation of core system functions and whose deletion would directly lead to system malfunctions or even crashes—into a kernel-level keep-alive list based on the operating system's fundamental operational requirements. Examples include system push service processes, system location service processes, system audio driver processes, and system network communication processes. This ensures basic system operation and prevents core processes from being deleted by low-memory killers or other malicious actors, thus preventing serious problems such as system paralysis and service interruptions.

[0066] Application-layer configuration: This refers to the process that users or application developers manually specify to keep alive at the application layer through visual interaction, configuration file editing, etc. It is a personalized and flexible way to configure the keep-alive list and a core configuration form to meet the differentiated needs of users. The key processes in application-layer configuration are mainly third-party application processes that meet the personalized needs of users, such as: music playback processes, background video playback processes, background processes of social applications, background download processes, etc.

[0067] Dynamic identification configuration: This refers to the kernel layer monitoring the running status and business characteristics of all running processes in the system in real time based on preset process characteristic identification rules. It automatically determines whether a process is a critical process and dynamically adds or removes processes from the keep-alive list. This is an intelligent configuration method for the keep-alive list, requiring no manual intervention or pre-entry; it is entirely automated by the kernel. The kernel layer can pre-set multi-dimensional process key characteristic judgment rules, which can be formulated around the core principles of whether a process has a significant impact on user experience and whether it is executing critical business functions. Core identification rules include, but are not limited to, whether a process continuously occupies core hardware resources, whether a process is executing critical business functions, the degree of user interaction related to the process, and the irreplaceability of the process's business functions.

[0068] In one alternative implementation, please refer to Figure 2 The process control method in this application embodiment further includes:

[0069] It provides a detection and removal call interface, which is used to provide a preset upper-layer application or service so that it can directly call the signal sending function.

[0070] When the detection mechanism is triggered, the upper-layer application or service predetermines the target process to be detected (e.g., ...). Figure 2 (Abnormal processes in the process) can be detected by directly calling the signal sending function through the kill call interface to send a kill signal to the target process.

[0071] For example, the timing of triggering the detection and removal mechanism includes: when the system resource utilization rate continuously exceeds a preset utilization threshold, or when a process is detected to be unresponsive for a duration exceeding a preset duration threshold, or when the user actively calls the detection and removal call interface.

[0072] The newly added detection and removal call interface in this embodiment is used to completely connect the kernel-mode signal sending function with the upper layer through AIDL and ioctl communication. This allows upper-layer applications or services to directly call the detection and removal method with the highest privileges at the lower layer, bypassing the permission check problem of traditional upper-layer detection and removal, thereby avoiding the problem of incomplete detection and removal caused by permission checks.

[0073] Secondly, embodiments of this application also provide a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the process control method as described above.

[0074] The above system can execute the methods provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing the methods.

[0075] Thirdly, Embodiment 4 of this application provides a computer-readable storage medium having computer-executable instructions stored thereon, which, when executed by a processor, implement the process control method provided in all embodiments of this application.

[0076] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0077] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0078] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0079] Computer program code for performing the operations of the embodiments of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0080] Finally, it should be noted that although the above embodiments have been described in the text and drawings of this application, this should not limit the scope of patent protection of this application. Any technical solutions that are based on the essential concept of this application and utilize the content described in the text and drawings of this application, resulting in equivalent structural or procedural substitutions or modifications, as well as the direct or indirect application of the technical solutions of the above embodiments to other related technical fields, are all included within the scope of patent protection of this application.

Claims

1. A process control method, characterized in that, include: Provide a keep-alive list, which stores information about critical processes that need to be kept alive; The kernel probe continuously monitors the signal sending function in the kernel. The signal sending function is at least used by the killing initiator to send a killing signal to the target process to be killed. When the kernel probe detects that the preset keep-alive conditions are met, it performs signal processing on the signal sending function so that the target process to be killed can be kept alive and not killed. The preset keep-alive conditions include: the signal currently sent by the signal sending function is a kill signal, and the target process to be killed exists in the keep-alive list.

2. The process control method according to claim 1, characterized in that, The preset keep-alive condition also includes: the current detection and killing initiator is a preset target entity.

3. The process control method according to claim 2, characterized in that, The entities that initiate the detection and removal include low memory killers, memory overflow killers, activity management services, and / or kill command tools; the preset target entities include low memory killers.

4. The process control method according to claim 1, characterized in that, The detection and elimination signal includes a termination signal; The kernel probe performs signal processing on the signal sending function to keep the target process alive and prevent it from being killed, including: Before the signal sending function is sent to the target process to be killed, the termination signal in the signal sending function is replaced with a continuation signal; wherein the termination signal is used to instruct the target process to terminate, and the continuation signal is used to instruct the target process to continue running.

5. The process control method according to claim 1, characterized in that, The critical processes are configured by the application layer, the system preset configuration, and / or the dynamic identification configuration.

6. The process control method according to claim 5, characterized in that, The key processes include: music process, system push service process, location service process, and / or background download process.

7. The process control method according to claim 1, characterized in that, Also includes: A detection and removal call interface is provided, which is used to provide a preset upper-layer application or service so that it can directly call the signal sending function; When the detection and removal mechanism is triggered, the preset upper-layer application or service determines the target process to be detected and removed, and directly calls the signal sending function through the detection and removal call interface to send a detection and removal signal to the target process.

8. The process control method according to claim 7, characterized in that, The detection and removal mechanism is triggered when: the system resource utilization rate continuously exceeds a preset utilization threshold, or a process is detected to be unresponsive for a duration exceeding a preset duration threshold, or the user actively calls the detection and removal interface.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the process control method as described in any one of claims 1-8.

10. A computer-readable storage medium having computer-executable instructions stored thereon, characterized in that, The computer-executable instructions are executed by a computer processor to implement the process control method as described in any one of claims 1-8.

Images