WO2019036906A1 - Système et procédé de suppression de faible mémoire sur la base de système android - Google Patents

Système et procédé de suppression de faible mémoire sur la base de système android Download PDF

Info

Publication number
WO2019036906A1
WO2019036906A1 PCT/CN2017/098520 CN2017098520W WO2019036906A1 WO 2019036906 A1 WO2019036906 A1 WO 2019036906A1 CN 2017098520 W CN2017098520 W CN 2017098520W WO 2019036906 A1 WO2019036906 A1 WO 2019036906A1
Authority
WO
WIPO (PCT)
Prior art keywords
processes
memory
priority
package name
low
Prior art date
Application number
PCT/CN2017/098520
Other languages
English (en)
Chinese (zh)
Inventor
邓强
Original Assignee
深圳传音通讯有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳传音通讯有限公司 filed Critical 深圳传音通讯有限公司
Priority to PCT/CN2017/098520 priority Critical patent/WO2019036906A1/fr
Publication of WO2019036906A1 publication Critical patent/WO2019036906A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the invention relates to a system memory management mechanism of an intelligent mobile terminal, in particular to a low memory killing system and method based on an Android system.
  • the Android (Android) system currently used in smart mobile terminals such as mobile phones is an open source operating system based on Linux system development.
  • the memory management of Linux system has its unique dynamic storage management mechanism, but the Android system is further optimized based on the memory management mechanism of Linux.
  • the Linux system will end the process after the process activity has stopped, and the Android system will keep these processes in memory.
  • the Android system is a multi-tasking system, which means that multiple processes can be run simultaneously. In general, it takes a certain amount of time to start a process, so in order to speed up the process, whenever the user exits a process, the Android system does not immediately stop the process completely (commonly known as killing the process). So that when the user chooses to run the process next time, they can start quickly. However, as more and more processes are reserved in the Android system, the memory will definitely be insufficient. At this time, the Android system will start the automatic killing process of the process, which is the most used and the least important to use.
  • Low Memory Low Memory Killer
  • the Android system has a total of six types of processes, and the possibility of being detected and stopped by the low memory killing mechanism is arranged from low to high, in order: foreground process, visible process, secondary process, background process, content provider And an empty process. That is to say, when the memory of the Android system is insufficient, the first process to be killed is an empty process (if it exists). If the empty process is still unable to guarantee enough memory space to maintain normal system operation after being killed, the second one will be the content provider. And so on, the next third will be the background process.
  • the front-end process, the visible process, and the secondary process are three types of processes in system memory management. In the process, the possibility of being killed by the low memory killing mechanism is very small, because once these processes are killed, it will result in a very poor user experience.
  • the Android system has a rule to reclaim the memory space. It has a predetermined threshold for the scheduling of the memory space. Only when the memory space of the system is lower than the threshold, the Android system will start the low memory killing mechanism.
  • the default rule order is to stop running the system that is considered to be the least important process, thus freeing up memory space.
  • the directory file of the smart mobile terminal using the Android system that is, the directory file of Sys/Module/Lowmemorykiller/Parameters/Minfree, and the corresponding threshold is recorded therein.
  • the running memory of the Android system is less than 211Mb
  • the low memory killing mechanism needs to kill the empty process
  • the running memory of the Android system is less than 176Mb
  • the low memory killing mechanism not only needs to kill the empty process, but also needs to be combined. Kill the content provider.
  • FIG. 1 it is a flowchart of the low memory killing mechanism in the prior art.
  • the specific killing process includes the following steps:
  • the low memory killing mechanism is only a mechanical traversal process list, select one of them. The lowest priority process is checked and killed. After the completion, it is judged whether the currently available memory has reached the expected level. If the expected memory has not been reached, repeat the above steps until the available memory reaches the expected value. Therefore, it has the following defects:
  • the object of the present invention is to provide a low memory killing system and method based on the Android system, which can quickly and effectively recover the system memory space by troubleshooting the associated process to completely remove the stubborn process cluster with correlation, so that the system can get the problem of the card. Timely mitigation, effectively improving the user experience and reducing system power consumption.
  • the present invention provides a low memory killing system based on an Android system, comprising: a memory detecting module, detecting in real time whether the memory space of the Android system reaches a set expected value; a low memory driving module, and a memory detecting module Connection, when the memory space of the Android system does not reach the set expected value, the lowest priority process is selected in all currently running processes; the process management service module is connected with the low memory driver module, and the priority is the lowest.
  • the process matches all currently running other processes, finds all associated processes that are related to the lowest priority process, and obtains a stubborn process cluster; the process kills the module, connects with the process management service module, and kills the stubborn process. All associated processes included in the cluster release the memory space occupied by the processes.
  • the low memory driver module includes: a first traversal unit connected to the memory detection module, and traversing and obtaining a list of processes of all currently running processes when the memory space of the Android system does not reach the set expected value; priority a sorting unit, configured to store a preset rule for sorting processes according to priority from high to low; a process screening unit respectively connected to the first traversal unit and the priority sorting unit, and provided by the priority sorting unit
  • the prioritization rule from the list of processes obtained by the first traversal unit, filters the process with the lowest priority.
  • the process management service module includes: a package name storage unit, connected to the process screening unit to obtain package name information of a process with the lowest priority; and a second traversal unit connected to the package name storage unit to traverse all processes currently running The process list, and obtain the package name information of each process in the process list; the comparison unit is respectively connected with the package name storage unit and the second traversal unit, and the package name information of each process in the process list is separately selected from the filtered The packet name information of the process with the lowest priority is compared, and the associated process in which all the package name information matches the process with the lowest priority is detected; the sensing judgment module is respectively connected with the comparison unit and the package name storage unit, and is currently not used by the user.
  • the package name information of the perceived association process is stored in the package name storage unit to obtain a stubborn process cluster.
  • the process killing module is connected to the package name storage unit in the process management service module, and all the processes corresponding to all the package name information stored therein are checked and killed.
  • the invention also provides a low memory killing method based on the Android system, based on the foregoing low memory killing system implementation, comprising the following steps:
  • the memory detection module detects in real time whether the memory space of the Android system reaches the set expected value; when the expected value is not reached, the execution of S2 is continued;
  • the low memory driver module filters out the lowest priority process among all currently running processes
  • the process management service module matches the lowest priority process with all currently running other processes, and finds all associated processes that are related to the lowest priority process, and obtains a stubborn process cluster;
  • the process killing module kills all associated processes included in the stubborn process cluster, releases the memory space occupied by the processes, and returns to execute S1.
  • the S1 includes the following steps:
  • the memory detection module compares the detected actual value of the current memory space of the Android system with the preset expected value; when the actual value of the memory space is greater than or equal to the expected value, returns to execute S12; when the actual value of the memory space is small Continue to execute S2 at the expected value.
  • the S2 includes the following steps:
  • the priority sorting unit stores a preset rule for sorting processes according to priority from high to low;
  • the first traversal unit traverses and acquires a list of processes of all processes currently running.
  • the process screening unit selects, according to the priority ordering rule stored in the priority sorting unit, the process with the lowest priority from the process list obtained by the first traversal unit.
  • the process is divided into large classes, and sorted according to the priority from high to low: foreground process, visible process, secondary process, background process, content provider and empty process;
  • each major class of processes is further divided into small classes, and sorted according to the priority from high to low: the process with the most recent maximum probability being restarted, and the recent Processes with a higher probability of being restarted, and processes that have not been restarted in the near future;
  • each process included in each small class process is sorted according to the priority from high to low.
  • the process with the shortest average startup time has the lowest priority and the average startup time is the most.
  • a long process with the highest priority is the highest priority.
  • the S3 includes the following steps:
  • the package name storage unit obtains the package name information of the process with the lowest priority.
  • the second traversal unit traverses the process list of all processes currently running, and obtains package name information of each process in the process list.
  • the comparison unit compares the package name information of each process in the process list with the package name information of the selected lowest priority process, and determines whether the package name information of the two matches, and if yes, confirms that the process is The associated process that matches the lowest priority process until all processes in the process list are checked;
  • the perceptual judgment module determines whether each associated process is perceived by the user; if yes, the associated process is added to the whitelist and discarded to clean up; if not, the package name information of the associated process is stored in the package name storage. In the unit, get a stubborn process cluster.
  • the rule for determining whether the association process is perceived by the user is specifically:
  • S343. Determine whether the associated process is a process of an invisible interface that is currently in an operating state. If yes, determine that the associated process is perceived by the user. If not, determine that the associated process is not perceived by the user.
  • the low memory memory killing system and method based on the Android system of the present invention has the following advantages compared with the prior art: it is related to the process of checking and killing by thoroughly checking the association process. All the stubborn process clusters, avoid repeated repeated invalid killing work, and quickly and effectively recover the system memory space, so that the system Karton problem is relieved in time, effectively improve the user experience, and reduce system power consumption.
  • FIG. 1 is a flow chart of a low memory killing mechanism based on an Android system in the prior art
  • FIG. 2 is a schematic diagram of a working architecture of a low memory killing system based on an Android system in the present invention
  • FIG. 3 is a schematic structural diagram of a low memory killing system based on an Android system in the present invention.
  • FIG. 4 is a schematic structural view of a low memory drive module in the present invention.
  • FIG. 5 is a schematic structural diagram of a process management service module in the present invention.
  • FIG. 6 is a basic flowchart of a low memory killing method based on an Android system in the present invention.
  • FIG. 7 is a detailed flowchart of a low memory killing method based on Android system in the present invention.
  • the terms “including”, “comprising”, “having”, or any other variants are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Includes other elements not explicitly listed, or elements that are inherent to such a process, method, item, or terminal device.
  • An element defined by the phrase “including” or “comprising” does not exclude the presence of additional elements in the process, method, article or terminal device including the element.
  • “greater than”, “less than”, “exceeded”, etc. are understood as not including the number; “above”, “below”, “inside”, etc. are understood to include the number.
  • FIG. 2 is a schematic diagram of a working architecture of a low-memory killing system based on an Android system provided by the present invention; wherein the Android system is generally applied to a mobile phone, or a tablet computer, or a smart wearable device (including smart
  • a mobile intelligent terminal such as a watch or a smart bracelet includes: a kernel driver layer (Kernel), which is a hardware driver running layer of a mobile intelligent terminal, and is an abstraction layer between hardware and software processes; a framework layer is The link layer between the application layer and the kernel driver layer; the application layer (App), where each application process in the mobile smart terminal runs.
  • Kernel kernel driver layer
  • App application layer
  • the schematic diagram of a low-memory killing system based on the Android system includes: a memory detecting module 1 , which detects in real time whether the memory space of the Android system reaches a set expected value; a low memory driver Module 2, which is disposed in the kernel driver layer of the Android system, is connected to the memory detecting module 1 and is filtered out in all currently running processes when the memory space of the Android system does not reach the set expected value.
  • the process with the lowest priority; the Process Management Service (AMS) module 3 is set in the framework layer of the Android system and is connected to the low memory driver module 2, and the process with the lowest priority and all other processes currently running. Perform matching, find all associated processes that are related to the lowest priority process, and obtain stubborn process clusters; process killing module 4, connect with process management service module 3, and kill all associated processes included in the stubborn process cluster , free up the memory space occupied by these processes.
  • AMS Process Management Service
  • the memory detecting module 1 the expected value (threshold value) of the memory space required for the normal operation of the Android system is stored. After detecting the actual value of the current memory space of the Android system, the memory detecting module 1 compares with the preset expected value; if the actual value of the memory space is greater than the expected value, the current memory space of the Android system reaches the set expectation. The value, that is, the memory space is sufficient; if the actual value of the memory space is less than the expected value, the current memory space of the Android system does not reach the set expected value, that is, the memory space is insufficient, and the memory detection module 1 will trigger the low memory driver. Module 2 starts, and needs to kill the lowest priority process or all associated processes related to the process, thereby freeing up the memory space occupied by the processes, so that the Android system can obtain the memory space required for normal operation.
  • FIG. 4 it is a schematic structural diagram of the low memory drive module 2, including: a first traversal unit 21 connected to the memory detection module 1 and traversing when the memory space of the Android system does not reach the set expected value. And obtaining a process list of all processes currently running; a priority sorting unit 22, configured to store a preset rule for sorting the processes according to priority from high to low; the process screening unit 23, respectively, and the first The traversing unit 21 and the priority sorting unit 22 are connected, and the process with the lowest priority is selected from the process list acquired by the first traversing unit 21 according to the priority ordering rule provided in the prioritizing unit 22.
  • the rules for sorting the processes according to the priorities from high to low are stored in the priority sorting unit 22, and specifically include: first, classifying the processes according to the Android system, and sorting the processes according to the priority from high to low. It is: foreground process, visible process, secondary process, background process, content provider and empty process; then, according to the number of startups of each process and the time consumed by each startup, each class process is further divided into subclasses.
  • the processes included in each small class process are sorted according to the priority from high to low, wherein the process with the shortest average startup time is given priority.
  • the process with the lowest level and the longest average startup time has the highest priority.
  • Foreground App refers to the process and some system processes currently displayed on the screen of the intelligent mobile terminal; in principle, such processes are almost impossible to be killed by the low memory killing system;
  • Representative process The app that the user is currently using to read the news, or the app that the user is currently using to browse the web.
  • Background Process is the process that is normally understood to be switched to the background after startup. That is to say, when the process is displayed on the screen of the smart mobile terminal, the process that it runs is the foreground process, and once the user presses the Home button (non-Back return key) to return to the main interface, the process is resident. In the background, become a background process. Usually such background processes are the target objects of the low memory killing system;
  • Representative process A game app that the user is running before. Because the user has other usage requirements for the smart mobile terminal, after pressing the Home button, the game app is switched to the background process.
  • Content Provider refers to no process entity, only provide content for other processes to use. In general, such a process is also the target of a low-memory killing system, which is very likely to be investigated and terminated.
  • the present invention prioritizes the priority of these six types of processes, in the actual application process, the foreground process, the visible process, and the secondary process are basically non-existent (but not absolutely) the possibility of being killed, and all the killing objects are concentrated in the three processes of background processes, content providers and empty processes.
  • the process first sorts the priorities according to the categories, further processing of each process included in each category is further performed.
  • the specific ordering rules are:
  • the average startup time of the process is calculated according to the following formula:
  • t avg represents the average startup time of the process
  • n represents the total number of times the process has recently started
  • t n represents the startup time of the process from the current time in the n starts.
  • each small class of processes included in each major process is sorted according to the priority from high to low: the process with the most recent maximum probability being restarted, the process with a recent high probability of being restarted, and will not be restarted in the near future. Process.
  • the priority is sorted from high to low according to the average startup time t avg of each process, wherein the process with the shortest startup time t avg has the lowest priority.
  • the process with the longest start-up time t avg has the highest priority.
  • the first traversal unit 21 traverses all the running process lists obtained, and there is only one empty process; the priority ordering unit 22 The priority ranking rule stored in the process belongs to the process with the lowest priority, and is directly filtered by the process screening unit 23.
  • the first traversal unit 21 traverses the obtained list of all running processes, there is no empty process, but there is only one content. Provider; according to the priority ranking rule stored in the prioritization unit 22, since there is no empty process running, the content provider becomes the process with the lowest priority and is filtered by the process screening unit 23.
  • the first traversal unit 21 traverses the obtained list of all running processes, there is no empty process, and there is no content provider. However, there are 3 background processes, and the 3 background processes belong to the process whose recent maximum probability is restarted, the process whose recent probability is restarted, and the process which will not be restarted in the near future;
  • the stored prioritization rule in which the process that will not be restarted in the near future belongs to the process with the lowest priority, is thus filtered by the process screening unit 23.
  • the first traversal unit 21 traverses the list of all running processes acquired, there is no empty process, and there is no content provider. However, there are 3 background processes, and these 3 background processes belong to the process that will not be restarted in the near future.
  • the priority is further sorted according to the average startup time of each process, and the process with the shortest average startup time is The lowest priority will be filtered by the process screening unit 23. When the average startup time of a process is the shortest, it indicates the initiation of the process.
  • the fastest speed, temporarily stop running, the time spent on the next restart is the shortest; therefore, the process that keeps the slow start speed continues to run in the background, selects the fastest startup process to check and kill, temporarily releases the memory. Space, even if the subsequent user starts the process again, it will not cause the startup time to be too long, so that the user experience can be improved.
  • FIG. 5 it is a schematic structural diagram of the process management service module 3, including: a package name storage unit 31, connected to the process screening unit 23, and acquiring package name information of a process with the lowest priority; the second traversal unit 32 Connected to the package name storage unit 31, after the package name storage unit 31 acquires the package name information of the process with the lowest priority, traverses the process list of all processes currently running, and acquires the package name information of each process in the process list.
  • the comparison unit 33 is connected to the package name storage unit 31 and the second traversal unit 32, respectively, and compares the package name information of each process in the process list with the package name information of the selected lowest priority process, and performs troubleshooting.
  • the perception determination module 34 is connected to the comparison unit 33 and the package name storage unit 31, respectively, and stores the package name information of the associated process that is not currently perceived by the user to In the package name storage unit 31, a stubborn process cluster is obtained.
  • the rule that the sensing determining module 34 determines whether the associated process is perceived by the user is: determining whether the associated process and the foreground process currently in the operating state belong to the same task, and if so, determining that the associated process is perceived by the user; otherwise, further determining Whether the associated process is a process of a visible interface in a non-operational state, and if so, the associated process is considered to be perceived by the user; otherwise, the process of determining whether the associated process is an invisible interface of the currently operating state is continued, and if so, the associated process is considered The user perceives, otherwise the associated process is considered not to be perceived by the user.
  • the process of the visible interface of the non-operational state may specifically be a process related to the use of the user, such as an input method.
  • the process of the invisible interface of the operating state may specifically be a process of playing music, or a process of performing a download task, etc., which does not need to be visible in the interface of the smart mobile terminal, but is currently being operated by the user. process.
  • the process killing module 4 is connected to the package name storage unit 31 in the process management service module 3, and all the processes corresponding to all the package name information stored therein are checked and killed, so as to completely eliminate the stubborn process cluster and prevent the stubborn process. Start again.
  • the present invention further provides a low memory killing method based on an Android system, which is based on the aforementioned low Memory killing system implementation, suitable for mobile smart devices such as mobile phones, or tablets, or smart wearable devices (including smart watches or smart bracelets), including the following steps:
  • the memory detection module 1 detects in real time whether the memory space of the Android system reaches the set expected value; when the expected value is not reached, triggering to start the low memory drive module 2, and continue to execute S2;
  • the low memory driver module 2 screens out the lowest priority process among all currently running processes
  • the process management service module 3 matches the lowest priority process with all currently running other processes, and finds all associated processes that are related to the lowest priority process to obtain a stubborn process cluster.
  • the process killing module 4 kills all associated processes included in the stubborn process cluster, releases the memory space occupied by the processes, and returns to execute S1.
  • the S1 includes the following steps:
  • the memory detecting module 1 compares the detected actual value of the current memory space of the Android system with the preset expected value.
  • the actual value of the memory space is greater than or equal to the expected value, it indicates that the current memory space of the Android system reaches the set expected value, that is, the memory space is sufficient, and the execution returns to S12;
  • the current memory space of the Android system does not reach the set expected value, that is, the memory space is insufficient, and S2 is continued.
  • the S2 includes the following steps:
  • the priority sorting unit 22 stores a preset rule for sorting the processes according to the priority from high to low;
  • the first traversal unit 21 traverses and acquires a process list of all processes currently running.
  • the process screening unit 23 selects the process with the lowest priority from the process list acquired by the first traversal unit 21 according to the priority ordering rule stored in the priority sorting unit 22.
  • the process is divided into large classes and sorted according to the priority from high to low: foreground process, visible process, secondary process, background process, content provider and empty process;
  • each major class of processes is further divided into small classes, and sorted according to the priority from high to low: the process with the most recent maximum probability being restarted, and the recent Processes with a higher probability of being restarted, and processes that have not been restarted in the near future;
  • each process included in each small class process is sorted according to the priority from high to low.
  • the process with the shortest average startup time has the lowest priority and the average startup time is the most.
  • a long process with the highest priority is the highest priority.
  • the present invention prioritizes the priority of these six types of processes, in the actual application process, the foreground process, the visible process, and the secondary process are basically non-existent (but It is not absolute) the possibility of being killed, and all the killing objects are concentrated in the three processes of background processes, content providers and empty processes.
  • t avg represents the average startup time of the process
  • t c represents the current time
  • t n represents the last startup time of the process from the current time in n starts
  • n represents the total number of times the process has recently started
  • the S3 includes the following steps:
  • the package name storage unit 31 acquires package name information of the process with the lowest priority.
  • the second traversal unit 32 traverses the process list of all processes currently running, and obtains package name information of each process in the process list.
  • the comparing unit 33 compares the package name information of each process in the process list with the package name information of the selected lowest priority process, and determines whether the package name information of the two matches, and if yes, confirms the process. Is the associated process that matches the lowest priority process until all processes in the process list are checked.
  • the perceptual judgment module 34 determines whether each associated process is perceived by the user; if yes, the associated process is added to the whitelist and discarded to clean up; if not, the package name information of the associated process is stored to the package name. In the storage unit 31, a stubborn process cluster is obtained.
  • the rule for determining whether the association process is perceived by the user is specifically:
  • S343. Determine whether the associated process is a process of an invisible interface that is currently in an operating state. If yes, determine that the associated process is perceived by the user. If not, determine that the associated process is not perceived by the user.
  • the process of the visible interface of the non-operational state may specifically be a process related to the use of the user, such as an input method.
  • the process of the invisible interface of the operating state may specifically be a process of playing music, or a process of performing a download task, etc., which does not need to be visible in the interface of the smart mobile terminal, but is currently being operated by the user. process.
  • the memory detecting module 1 detects that the memory space of the Android system does not reach the set expected value, triggering and starting the low memory driving module 2; the low memory driving module 2 filters out all current
  • the only one empty process in the running process list is the process with the lowest priority. After the process management service module 3 is checked, no related process has been found. Therefore, the process killing module 4 will be empty. Process killing cleanup.
  • the memory detection module 1 detects that the memory space of the Android system has not reached the set expected value, and continues to be filtered by the low memory driver module 2, and no empty process is found, and no content is found.
  • the donor but finds 4 background processes, in which 4 low-priority processes that will not be restarted in the near future are filtered out, and then the average startup time is selected in the 2 processes.
  • the process which is the lowest priority process, is reported to the process management service module 3. After the process management service module 3 is checked, a number of associated processes with which correlations are found are found, and all associated processes are not perceived by the user, so the process killing module 4 includes the stubborn process cluster (including the lowest priority process and its All associated processes) are all cleaned up.
  • the low memory driver module 2 filters out another background process whose average startup time is long and will not be restarted in the near future is the lowest priority process, and is managed by the process.
  • the service module 3 is checked, an associated process with which it has relevance is found. However, the association process is determined to be perceived by the user after being judged, so the associated process is abandoned and killed, and the final process killing module 4 only kills the process with the lowest priority. Subsequently, it was found that the memory space of the Android system has reached the set expected value, and the process of killing and killing the process will not be performed temporarily.
  • the low-memory killing system and method based on the Android system triggers a low-memory driver module by setting a connection communication channel of the process management service module 3 between the low-memory driver module 2 and each process.
  • the process management service module 3 matches all the processes with the lowest priority by matching the package name information.
  • the sexual association process acquires the stubborn process cluster, so that the process killing module 4 can clean up and clean it up at one time, prevent the stubborn process cluster from starting again, and effectively improve the effect of memory recycling.
  • the associated process needs to be judged by the user, and when it is found that it is being perceived by the user, it is forgotten to be cleaned up.
  • the low memory killing system and method based on the Android system of the present invention has the following advantages: by checking the association process, completely removing all stubborn process clusters that are related to the process that needs to be killed and killed. Avoid repeated repeated invalidation and killing work, and quickly and effectively recover the system memory space, so that the system can be relieved in time, effectively improve the user experience, and reduce system power consumption.

Abstract

L'invention concerne un système et un procédé de suppression de faible mémoire sur la base de système sur la base de système Android, ledit procédé comprenant les étapes suivantes : S1. un module de détection de mémoire détecte, en temps réel, si un espace mémoire d'un système Android atteint une valeur attendue définie ; exécute S2 lorsque la valeur attendue n'est pas atteinte ; S2. le module d'entraînement à faible mémoire sélectionne, parmi tous les processus en cours d'exécution, un processus ayant la priorité la plus basse ; S3. un module de service de gestion de processus met en correspondance le processus ayant la priorité la plus basse avec d'autres processus en cours d'exécution, et sélectionne des processus associés mis en corrélation avec le processus ayant la priorité la plus basse, de façon à acquérir une grappe de traitement persistante ; S4. un module de suppression de processus supprime le groupe de processus persistant, libérant un espace mémoire occupé par ces processus, et retournant à l'exécution S1. En sélectionnant les processus associés pour éliminer complètement les groupes de processus persistants corrélés, l'invention peut recycler rapidement et efficacement l'espace mémoire du système, ce qui permet de résoudre rapidement le problème du système étant bloqué, améliorant efficacement l'expérience de l'utilisateur et réduisant la consommation d'énergie du système.
PCT/CN2017/098520 2017-08-22 2017-08-22 Système et procédé de suppression de faible mémoire sur la base de système android WO2019036906A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/098520 WO2019036906A1 (fr) 2017-08-22 2017-08-22 Système et procédé de suppression de faible mémoire sur la base de système android

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/098520 WO2019036906A1 (fr) 2017-08-22 2017-08-22 Système et procédé de suppression de faible mémoire sur la base de système android

Publications (1)

Publication Number Publication Date
WO2019036906A1 true WO2019036906A1 (fr) 2019-02-28

Family

ID=65439363

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/098520 WO2019036906A1 (fr) 2017-08-22 2017-08-22 Système et procédé de suppression de faible mémoire sur la base de système android

Country Status (1)

Country Link
WO (1) WO2019036906A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103544063A (zh) * 2013-09-30 2014-01-29 三星电子（中国）研发中心 应用于安卓平台的进程清除方法和装置
CN104391743A (zh) * 2014-11-26 2015-03-04 北京奇虎科技有限公司 优化移动终端的运行速度的方法和装置
CN104503841A (zh) * 2014-12-15 2015-04-08 北京奇虎科技有限公司 进程清理方法及装置
US20150347181A1 (en) * 2014-05-30 2015-12-03 Apple Inc. Resource management with dynamic resource policies

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103544063A (zh) * 2013-09-30 2014-01-29 三星电子（中国）研发中心 应用于安卓平台的进程清除方法和装置
US20150347181A1 (en) * 2014-05-30 2015-12-03 Apple Inc. Resource management with dynamic resource policies
CN104391743A (zh) * 2014-11-26 2015-03-04 北京奇虎科技有限公司 优化移动终端的运行速度的方法和装置
CN104503841A (zh) * 2014-12-15 2015-04-08 北京奇虎科技有限公司 进程清理方法及装置

Similar Documents

Publication Publication Date Title
CN106354562B (zh) 内存清理系统和内存清理方法
US11099900B2 (en) Memory reclamation method and apparatus
CN103164268B (zh) 系统优化方法及装置
CN107526640B (zh) 资源管理方法、装置、移动终端及计算机可读存储介质
WO2017211226A1 (fr) Procédé d'affichage de fichier multimédia, terminal, et support d'informations
WO2017084293A1 (fr) Procédé, dispositif et équipement électronique de fermeture d'application
CN103092700A (zh) 内存清理方法、装置和终端设备
WO2014029299A1 (fr) Procédé et appareil de sauvegarde d'informations
TWI628588B (zh) 內存清理系統、方法及終端設備
CN103699420A (zh) 系统恢复方法和系统恢复装置
CN106445604A (zh) 一种应用程序的清理方法和装置
CN106354601A (zh) 数据分区的存储空间管理方法及装置
CN111258921A (zh) 垃圾内存回收方法及装置、电子设备、存储介质
CN108804207A (zh) 一种基于Android系统的进程管控方法
CN107615250A (zh) 一种针对应用的处理方法、装置及智能终端
CN109117263B (zh) 一种用户终端内存释放的方法及装置
CN110737606B (zh) 内存回收处理方法、装置、电子设备以及存储介质
WO2017185263A1 (fr) Procédé et appareil de récupération de mémoire
CN110162563A (zh) 一种数据入库方法、系统及电子设备和存储介质
WO2019036906A1 (fr) Système et procédé de suppression de faible mémoire sur la base de système android
CN112307381A (zh) 一种页面加载的方法、装置、存储介质以及电子设备
US11068375B2 (en) System and method for providing machine learning based memory resiliency
CN111221650A (zh) 基于进程类型关联的系统资源回收方法及装置
CN104834553A (zh) 一种用户终端的业务并发处理方法及用户终端
CN100589417C (zh) 处理电信网管系统拓扑界面大量上报消息的系统和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17922459

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17922459

Country of ref document: EP

Kind code of ref document: A1