CN107908478B - Memory cleaning method, mobile terminal and computer readable storage medium - Google Patents
Memory cleaning method, mobile terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN107908478B CN107908478B CN201711247486.9A CN201711247486A CN107908478B CN 107908478 B CN107908478 B CN 107908478B CN 201711247486 A CN201711247486 A CN 201711247486A CN 107908478 B CN107908478 B CN 107908478B
- Authority
- CN
- China
- Prior art keywords
- memory
- preset
- state value
- mobile terminal
- blocked
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
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]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5022—Mechanisms to release resources
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a memory cleaning method, a mobile terminal and a computer readable storage medium, which can automatically clean the memory occupied resources of the blocked process when the process is detected to be blocked and the blockage cannot be solved by detecting the preset process of the mobile terminal, executing a preset processing strategy to process the blocked process when the preset process is detected to be blocked, further detecting whether the blocked preset process is recovered to be normal after the preset processing strategy is executed, then judging whether the memory of the mobile terminal is abnormal or not based on the memory operation information of the blocked preset process when the blocked preset process is not recovered to be normal or not, determining the blocked preset process as the process to be cleaned when the memory occupied resources of the process to be cleaned are cleaned, and reserving abundant memory.
Description
Technical Field
The present invention relates to the field of mobile terminal technologies, and in particular, to a memory cleaning method, a mobile terminal, and a computer-readable storage medium.
Background
With the development of mobile terminal technology, more and more APPs (applications) are integrated in the mobile terminal, and at present, tens of thousands of applications based on different scenes of the mobile terminal are provided, and more third-party applications and service software are installed on the mobile terminal by a user. When the third-party application and the service software are started, memory resources need to be allocated to a process running the third-party application and the service software, and when the process is blocked, the memory resources occupied by the process cannot be released.
At present, a common solution that a mobile terminal cannot start a new third-party application or service software due to insufficient memory resources of the mobile terminal is to manually clear a memory of the mobile terminal by a user, but the user can only clear all memory occupied resources in the memory, and cannot only clear the memory occupied resources of a blocked process, so that how to automatically clear the memory occupied resources of the blocked process in the memory when the process is blocked is an urgent problem to be solved at present.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a memory cleaning method, a mobile terminal and a computer readable storage medium, and aims to solve the technical problem of how to automatically clean the memory occupied resources of a blocked process in a memory and reserve sufficient memory when the process is blocked.
In order to achieve the above object, the present invention provides a memory cleaning method, including the following steps:
when the preset process of the mobile terminal is detected to be blocked, executing a preset processing strategy, and after the preset processing strategy is executed, detecting whether the blocked preset process is recovered to be normal or not;
when the situation that the blocked preset process is not recovered to be normal is detected, acquiring the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the memory of the mobile terminal is abnormal, determining the blocked preset process as a process to be cleaned, and cleaning the memory occupied resources of the process to be cleaned.
Optionally, the step of determining whether the memory of the mobile terminal is abnormal according to the memory operation information includes:
reading the memory application information, the memory address information and the memory mapping information of the blocked preset process from the memory operation information;
judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are all preset state values or not;
when the memory application state value, the memory address state value and the memory mapping state value are all preset state values, judging that the memory of the mobile terminal is not abnormal;
and when the memory application state value, the memory address state value and the memory mapping state value are not uniform to be preset state values, judging that the memory of the mobile terminal is abnormal.
Optionally, before the step of executing the preset processing policy, the memory cleaning method further includes:
monitoring a preset process of the mobile terminal to obtain process monitoring data, and judging whether the preset process is blocked according to the process monitoring data;
and executing the preset processing strategy when the preset process is blocked, and detecting whether the blocked preset process is recovered to be normal or not after the preset processing strategy is executed.
Optionally, the step of determining whether the preset process is blocked according to the process monitoring data includes:
reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set or not;
and when the process state value is not in the preset process state value set, judging that the preset process is blocked.
Optionally, after the step of monitoring a preset process of the mobile terminal to obtain process monitoring data and determining whether the preset process is blocked according to the process monitoring data, the memory cleaning method further includes:
writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at preset time intervals;
judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
and when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database.
Optionally, the step of cleaning the memory occupied resources of the process to be cleaned includes:
calculating the size of the memory occupied resources of each process to be cleaned, and determining the release sequence of the memory occupied resources of each process to be cleaned according to the size of the memory occupied resources of each process to be cleaned;
and releasing the memory occupied resources of each process to be cleaned according to the release sequence.
Optionally, after the step of determining whether the memory of the mobile terminal is abnormal according to the memory operation information, the memory cleaning method further includes:
when the memory of the mobile terminal is abnormal, obtaining blocking information, and outputting the blocking information and the memory operation information to a feature log file.
In addition, to achieve the above object, the present invention also provides a mobile terminal, including: the memory cleaning program is used for realizing the steps of the memory cleaning method when being executed by the processor.
The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a memory cleaning program, and the memory cleaning program implements the steps of the memory cleaning method when executed by a processor.
The invention provides a memory cleaning method, a mobile terminal and a computer readable storage medium, the invention detects the preset process of the mobile terminal, when the preset process is detected to be blocked, the preset processing strategy is executed to process the blocked process, and after the preset processing strategy is executed, whether the blocked preset process is recovered to be normal is further detected, then when the blocked preset process is detected not to be recovered to be normal, whether the memory of the mobile terminal is abnormal is judged based on the memory operation information of the blocked preset process, when the memory of the mobile terminal is abnormal, the blocked preset process is determined as the process to be cleaned, and the memory occupied resource of the process to be cleaned is cleaned, so that the memory occupied resource of the blocked preset process can be automatically cleaned when the process is detected to be blocked and the blockage can not be solved, the mobile terminal can automatically clear the resources occupied by the memory in the blocked process in the memory, and reserve abundant memory.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention;
FIG. 2 is a level diagram of an operating system of the mobile terminal according to the present invention;
FIG. 3 is a flowchart illustrating a memory cleaning method according to a first embodiment of the present invention;
FIG. 4 is a flowchart illustrating a memory cleaning method according to a second embodiment of the present invention;
FIG. 5 is a schematic view of a detailed flow chart of the step of determining whether the preset process is blocked according to the process monitoring data in FIG. 4;
fig. 6 is a flowchart illustrating a memory cleaning method according to a third embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.
The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 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, or other volatile solid state storage device.
Referring to fig. 2, which is a schematic hierarchical diagram of an operating system stored in a storage program area, as shown in fig. 2, the operating system includes a Loader layer, a Kernel layer, a Native layer, a Framework layer (including a C + + Framework layer and a Java Framework layer), and an App layer, where an HAL layer (hardware abstraction layer) also exists between the Kernel layer and the Native layer, a JNI layer also exists between the C + + Framework layer and the Java Framework layer, and a SysCall layer also exists between the HAL layer and the Kernel layer.
The Loader layer comprises a Boot ROM (Boot service) and a Boot Loader (Boot initialization program), wherein the Boot ROM is mainly used for booting by pressing a Power (Boot) key for a long time when the mobile terminal is in a Power-off state, and a Boot chip starts to execute from a preset code solidified in the ROM. The Boot Loader is a Boot program before starting the operating system, and mainly has the functions of checking the RAM, initializing hardware parameters and the like.
The Kernel layer is mainly used for performing related work such as initialization process management, memory management, Display loading, Camera Driver (Camera Driver), Binder Driver (Binder Driver) and the like, and is used for creating Kernel daemon processes such as Kernel worker threads kworkder, soft interrupt threads ksofirqd and soft interrupt threads thermal.
The Native layer mainly comprises a daemon process of a user space hatched by init, a HAL layer, startup animation and the like. User daemon processes, User Daemons, such as ueven, logd, health, installd, adbd, and lmkd, can hatch out from the Init process (a User-level process started by a kernel); the init process also starts important services such as servicemanager and bootanim; the init process hatches a Zygote process, the Zygote process is the first Java process of the operating system, the Zygote process is the parent process of all the Java processes, and the Zygote process is hatched from the init process.
The Framework layer comprises a Zygote process, a System Server (System service) process and a Media Server (multimedia service) process, wherein the Zygote process is generated by an init process through analysis of an init.rc file and then fork, and mainly comprises loading Zygote init classes, registering Zygote Socket service end sockets, loading virtual machines, preloadClasses, preloadResouces and the like; the System Server process is derived from a Zygote process fork, the System Server is the first process of Zygote incubation, and the System Server is responsible for starting and managing the whole Java Framework and comprises services such as an ActivitiManager (application program component), a PowerManager (power supply management component) and a WindowManagerServer (window management component); the Media Server process, which is derived from the init process fork, is responsible for starting and managing the whole C + + frame, and includes services such as audio pointer (afofinger), Camera Service (Camera Service), and MediaPlayServer (multimedia Service).
The APP layer comprises APP processes, each APP process is generated by a Zygote process fork, the first APP process hatched by the Zygote process is a Launcher (desktop Launcher), desktop APPs seen by a user are created by the Zygote process, the App processes such as a Browser, a Phone and an Email are also created by the Zygote process, and each App runs on at least one process.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
Based on the above mobile terminal hardware structure, various embodiments of the mobile terminal of the present invention are provided.
Referring to fig. 1, in a first embodiment of the mobile terminal of the present invention, the mobile terminal includes: a memory, a processor, and a memory cleaner stored on the memory and operable on the processor, the memory cleaner when executed by the processor implementing the steps of:
when the preset process of the mobile terminal is detected to be blocked, executing a preset processing strategy, and after the preset processing strategy is executed, detecting whether the blocked preset process is recovered to be normal or not;
when the situation that the blocked preset process is not recovered to be normal is detected, acquiring the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the memory of the mobile terminal is abnormal, determining the blocked preset process as a process to be cleaned, and cleaning the memory occupied resources of the process to be cleaned.
Further, when executed by the processor, the memory cleaner further performs the following steps:
reading the memory application information, the memory address information and the memory mapping information of the blocked preset process from the memory operation information;
judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are all preset state values or not;
when the memory application state value, the memory address state value and the memory mapping state value are all preset state values, judging that the memory of the mobile terminal is not abnormal;
and when the memory application state value, the memory address state value and the memory mapping state value are not uniform to be preset state values, judging that the memory of the mobile terminal is abnormal.
Further, when executed by the processor, the memory cleaner further performs the following steps:
monitoring a preset process of the mobile terminal to obtain process monitoring data, and judging whether the preset process is blocked according to the process monitoring data;
and executing the preset processing strategy when the preset process is blocked, and detecting whether the blocked preset process is recovered to be normal or not after the preset processing strategy is executed.
Further, when executed by the processor, the memory cleaner further performs the following steps:
reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set or not;
and when the process state value is not in the preset process state value set, judging that the preset process is blocked.
Further, when executed by the processor, the memory cleaner further performs the following steps:
writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at preset time intervals;
judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
and when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database.
Further, when executed by the processor, the memory cleaner further performs the following steps:
calculating the size of the memory occupied resources of each process to be cleaned, and determining the release sequence of the memory occupied resources of each process to be cleaned according to the size of the memory occupied resources of each process to be cleaned;
and releasing the memory occupied resources of each process to be cleaned according to the release sequence.
Further, when executed by the processor, the memory cleaner further performs the following steps:
when the memory of the mobile terminal is abnormal, obtaining blocking information, and outputting the blocking information and the memory operation information to a feature log file.
The embodiment of the mobile terminal of the present invention is substantially the same as the embodiments of the memory cleaning method described below, and will not be described herein again.
Further, the present invention also provides a memory cleaning method applied to the mobile terminal shown in fig. 1, referring to fig. 3, and fig. 3 is a flowchart illustrating a first embodiment of the memory cleaning method according to the present invention.
In this embodiment, the memory cleaning method includes:
step S101, when detecting that the preset process of the mobile terminal is blocked, executing a preset processing strategy, and after executing the preset processing strategy, detecting whether the blocked preset process is recovered to be normal;
the memory cleaning method is applied to the mobile terminal shown in fig. 1, and the mobile terminal comprises a smart phone, a tablet computer and the like. The invention classifies the process required by starting the third-party application and service software by the SystemServer process according to the importance and the degree of dependence, obtains the most important process required by starting the third-party application and service software for the SystemServer process through classification and carding, and respectively comprises a Zygote process, a MediaServer process and a SurfaceFlinger process, and then the Zygote process, the MediaServer process and the SurfaceFlinger process need to be monitored. Therefore, the invention ensures that the monitoring process is deployed in the Java framework layer, runs in the form of an independent process, and adjusts the starting sequence to be executed before the Zygote process, the SurfaceFlinger process and the MediaServer process of the Java framework layer are formally started. In addition, the invention also establishes a daemon process on the Native layer for detecting whether the monitoring process operated by the Java framework layer is abnormal or not and recovering after the abnormality occurs, specifically, the daemon process actively initiates heartbeat communication with the monitoring process at regular time to judge whether the monitoring process normally operates or not, the heartbeat communication mainly comprises the steps of reading the state of the monitoring process through the Native layer daemon process, judging whether the monitoring process normally operates or not according to the read state, timing when the daemon process reads that the state of the monitoring process is in a blocking state, forcibly closing the monitoring process when the blocking state reaches a preset time, and reestablishing the monitoring process to ensure that the monitoring process is always in a normal working state.
The mobile terminal detects preset processes, namely a Zygote process, a MediaServer process and a SurfaceFlinger process, when any one of the Zygote process, the MediaServer process and the SurfaceFlinger process is detected to be blocked, executes a preset processing strategy, namely sending a process freezing request to a Kernel layer, namely a Kernel layer, of the mobile terminal, and freezes other processes except a system Kernel process, namely a System Server process and the blocked Zygote process, the MediaServer process and/or the SurfaceFlinger process through the Kernel layer. After executing the preset processing strategy, detecting whether the blocked preset process is recovered to be normal, namely detecting whether the blocked Zygote process, MediaServer process and/or SurfaceFlinger process is recovered to be normal or not, if the blocked Zygote process, MediaServer process and/or SurfaceFlinger process is not recovered to be normal, indicating that the preset processing strategy cannot solve the current blocking problem, and if the blocked Zygote process, MediaServer process and/or SurfaceFlinger process is recovered to be normal, indicating that the preset processing strategy can solve the current blocking problem.
Step S102, when detecting that the blocked preset process is not recovered to be normal, obtaining the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the mobile terminal detects that the blocked preset process, namely the Zygote process, the MediaServer process and/or the SurfaceFlinger process, does not return to normal, the mobile terminal acquires the memory running information of the blocked preset process, namely the Zygote process, the MediaServer process and/or the SurfaceFlinger process, and judges whether the memory of the mobile terminal is abnormal or not according to the memory running information, wherein the memory running information comprises a process identifier, memory application information, memory address information and memory mapping information.
Specifically, in the present embodiment, step S102 includes:
reading the memory application information, the memory address information and the memory mapping information of the blocked preset process from the memory operation information;
judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are all preset state values or not;
when the memory application state value, the memory address state value and the memory mapping state value are all preset state values, judging that the memory of the mobile terminal is not abnormal;
and when the memory application state value, the memory address state value and the memory mapping state value are not uniform to be preset state values, judging that the memory of the mobile terminal is abnormal.
When the mobile terminal detects that the Zygote process, the MediaServer process and/or the SurfaceFlinger process do not return to normal, reading the memory application information, the memory address information and the memory mapping information of the Zygote process, the MediaServer process and/or the SurfaceFlinger process from the memory running information of the blocked preset process, namely the Zygote process, the MediaServer process and/or the SurfaceFlinger process, then judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are preset state values, and if the memory application state value, the memory address state value and the memory mapping state value are preset state values, judging that the memory of the mobile terminal does not have abnormality; if the memory address state value and the memory mapping state value of the memory application state value are not uniform to preset state values, it can be determined that the memory of the mobile terminal is abnormal. If the memory application state value is a preset state value, it indicates that a memory application of a blocked Zygote process, a MediaServer process and/or a SurfaceFlinger process is abnormal, if the memory address state value is a preset state value, it indicates that the blocked Zygote process, the MediaServer process and/or the SurfaceFlinger process cannot read data in a memory address, and if the memory mapping state value is a preset state value, it indicates that a mapping relationship between an anonymous shared memory of the blocked Zygote process, the MediaServer process and/or the SurfaceFlinger process and a physical memory is abnormal. The memory application state value, the memory address state value and the memory mapping state value all include a first state value 1 and a second state value 0, and in this embodiment, the preset state value is 1.
Step S103, when the memory of the mobile terminal is abnormal, the blocked preset process is determined as a process to be cleaned, and the memory occupied resources of the process to be cleaned are cleaned.
When the blocked preset process, namely the zygate process, the MediaServer process and/or the surfefinger process, does not return to normal and the memory application state value, the memory address state value and the memory mapping state value in the memory operation information of the blocked preset process, namely the zygate process, the MediaServer process and/or the surfefinger process are not uniform to be the preset state values, the blocked preset process is determined as the process to be cleaned and the memory occupied resources of the process to be cleaned are cleaned, specifically, the memory of the mobile terminal is scanned according to the preset resource type to obtain the memory scanning data and the process identification information of the process to be cleaned, and then the memory occupied resources related to the process identification information are obtained from the memory scanning data and released. The occupied resources of the preset resource type comprise occupied resources of a System class, occupied resources of an application class, occupied resources of an object class, occupied resources of a database class and occupied resources of an asset class, wherein the occupied resources of the System class comprise resources of a Native Heap, a Dalvik Other, a Stack, an Ashmem, an Other dev, a so mmap, an apk mmap, a ttf mmap, a dex mmap, an at mmap, an art mmap, an Other mmap, a GL mtrack, an Unknown and the like, the occupied resources of the application class comprise resources of a Java Heap Stack, a Native ap Hep Stack, a Code pointer, a Stack, Graphics, a Private Other, a System and the like, the occupied resources of the object class comprise resources of a Views, applications, assexts, Local, coordinates, a park, a export, a library, and the like, and the occupied resources of the object class comprise resources of a View, asset class, resource of the resource class, the resource of the resource class comprise occupied resources of a View, asset class, resource of the resource, the import _ recipient class, the resource and the resource of the resource comprises resource of the resource type. It should be noted that the preset threshold may be set by a person skilled in the art based on actual situations, and the embodiment does not specifically limit this.
In this embodiment, the present invention detects a preset process of a mobile terminal, when it is detected that the preset process is blocked, executes a preset processing policy to process the blocked process, and further detects whether the blocked preset process is normal after executing the preset processing policy, and then when it is detected that the blocked preset process is not normal, judges whether a memory of the mobile terminal is abnormal based on memory operation information of the blocked preset process, and when the memory of the mobile terminal is abnormal, determines the blocked preset process as a process to be cleaned, and cleans up memory occupied resources of the process to be cleaned, so that when the process is detected to be blocked and the blockage cannot be solved, the memory occupied resources of the blocked preset process can be automatically cleaned up, and the mobile terminal automatically cleans up the memory occupied resources of the blocked process in the memory, and reserving abundant memory.
Further, referring to fig. 4, a second embodiment of the memory cleaning method according to the present invention is provided based on the first embodiment, and the difference from the foregoing embodiment is that before the step S101, the memory cleaning method further includes:
step S104, monitoring a preset process of the mobile terminal to obtain process monitoring data, and judging whether the preset process is blocked according to the process monitoring data;
when the preset process is blocked, executing step S101, that is, executing a preset processing policy, and after executing the preset processing policy, detecting whether the blocked preset process is recovered to normal.
It should be noted that, the present embodiment provides a specific way to detect whether a preset process of the mobile terminal is blocked based on the foregoing embodiment, which is only described below, and other references may be made to the foregoing embodiment.
The method comprises the steps of monitoring preset processes of the mobile terminal, namely a Zygote process, a MediaServer process and/or a SurfaceFlinger process, so as to obtain process monitoring data of the Zygote process, the MediaServer process and/or the SurfaceFlinger process, and judging whether at least one process in the Zygote process, the MediaServer process and/or the SurfaceFlinger process is blocked according to the process monitoring data.
Specifically, referring to fig. 5, fig. 5 is a detailed flowchart of step S104 shown in fig. 4, where the step S104 includes:
step S1041, reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set;
step S1042, when the process state value is in a preset process state value set, determining that the preset process is blocked, and when the process state value is not in the preset process state value set, determining that the preset process is not blocked.
After acquiring the process monitoring data, the mobile terminal reads a preset process, that is, a process state value of a zygate process, a MediaServer process and/or a surfafinger process, from the process monitoring data, and determines whether the process state value is in a preset process state value set, that is, determines whether the process state value of the zygate process, the MediaServer process and/or the surfafinger process is in the preset process state value set, if the process state value of the zygate process, the MediaServer process and/or the surfafinger process is in the preset process state value set, it may be determined that the zygate process, the MediaServer process and/or the surfafinger process is blocked, and if the process state value of the zygate process, the MediaServer process and/or the surfafinger process is not in the preset process state value set, it may be determined that the zygate process, the MediaServer process and/or the surfafinger process is not blocked. The process state value comprises Blocked, hell by, Active and watching Timeout and the like, and the preset process state value is a set consisting of the Blocked and the hell by.
In this embodiment, the present invention can quickly determine the state of the zygate process, the MediaServer process, and/or the surfaceflag process by reading the process state value of the zygate process, the MediaServer process, and/or the surfaceflag process, so as to quickly monitor the blocked process.
Further, referring to fig. 6, a third embodiment of the memory cleaning method according to the present invention is proposed based on the first or second embodiment, and the difference from the foregoing embodiment is that after the step S104, the memory cleaning method further includes:
step S105, writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at intervals of preset time;
step S106, judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
and step S107, when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database.
It should be noted that, based on the foregoing embodiments, the present invention provides a specific redundancy elimination method for process monitoring data, which is only described below, and other embodiments can be referred to.
The mobile terminal writes the process monitoring data into a monitoring database after acquiring the process monitoring data, reads the process monitoring data from the monitoring database at intervals of preset time, judges whether the process monitoring data is redundant data according to the process state value of a preset process, namely a Zygote process, a MediaServer process and/or a SurfaceFlinger process, in the process monitoring data, and deletes the process monitoring data from the monitoring database when the process monitoring data is redundant data.
In particular, the process state value of the preset process is obtained from the process monitoring data, namely the process state value of the Zygote process, the MediaServer process and/or the SurfaceFlinger process is obtained from the process monitoring data, and judging whether at least one process state value in the process state values of the Zygote process, the MediaServer process and/or the SurfaceFlinger process is in a preset process state value set, if there is at least one process status value among the process status values of the zygate process, the MediaServer process and/or the surfaceflag process that is not in the preset set of process status values, it may be determined that the process monitor data is redundant, and, therefore, the process monitor data is deleted from the monitor database, if none of the process state values of the zygate process, the MediaServer process and/or the surfefinger process is in the preset set of process state values, it may be determined that the process monitor data is not redundant data and, therefore, the process monitor data is retained.
In this embodiment, the process monitoring data is subjected to redundancy removal processing at preset intervals, so that the data recorded in storage can be effectively reduced, the occupation of disk space is reduced, and the utilization rate of a disk is improved.
Further, based on the first, second or third embodiment, a fourth embodiment of the memory cleaning method of the present invention is provided, which is different from the foregoing embodiment in that the step S103 includes:
calculating the size of the memory occupied resources of each process to be cleaned, and determining the release sequence of the memory occupied resources of each process to be cleaned according to the size of the memory occupied resources of each process to be cleaned;
and releasing the memory occupied resources of each process to be cleaned according to the release sequence.
It should be noted that, based on the foregoing embodiments, the present invention provides a specific way to release resources occupied by a memory, which is described below only, and other references may be made to the foregoing embodiments.
The mobile terminal calculates the size of the memory occupied resource of each process to be cleaned, determines the release sequence of the memory occupied resource of each process to be cleaned according to the size of the memory occupied resource of each process to be cleaned, and then releases the memory occupied resource of each process to be cleaned according to the release sequence.
In this embodiment, the method and the device for clearing the memory occupied resources of the processes to be cleared determine the clearing sequence of the memory occupied resources of each process to be cleared based on the size of the memory occupied resources of each process to be cleared, so that the mobile terminal can clear the memory occupied resources of each process to be cleared based on the clearing sequence, and the memory resource release rate is effectively improved.
Further, based on the first, second or third embodiment, a fifth embodiment of the memory clearing method of the present invention is provided, which is different from the foregoing embodiment in that after step S103, the memory clearing method further includes:
when the memory of the mobile terminal is abnormal, obtaining blocking information, and outputting the blocking information and the memory operation information to a feature log file.
When the preset process with the blockage, namely the Zygote process, the MediaServer process and/or the SurfaceFlinger process, does not return to normal and the memory application state value, the memory address state value and the memory mapping state value in the memory running information of the preset process with the blockage, namely the Zygote process, the MediaServer process and/or the SurfaceFlinger process are not uniform to be the preset state values, the blockage information is obtained and the blockage information and the memory running information are output to the feature log file, specifically, the mobile terminal independently creates a thread to output the blockage information and the memory running information to the Debusord process, and the Debusord process directionally outputs the blockage information and the memory running information to the feature log file with the Debusger authority processing.
In specific implementation, the characteristic log file is stored in a preset storage area, the mobile terminal reads the characteristic log file from the preset storage area at regular time, whether the bit number of the characteristic log file is larger than or equal to a preset bit number is judged, then when the bit number of the characteristic log file is larger than or equal to the preset bit number, the characteristic log file in the preset storage area is uploaded to a preset cloud end to be stored, the characteristic log file which is uploaded successfully is deleted from the preset storage area, the characteristic log file can be uploaded to the cloud end to be stored when the characteristic log file exceeds a certain bit number, and the utilization rate of a disk is improved.
In this embodiment, the present invention outputs the blocking information and the memory operation information to the feature log file, which facilitates subsequent searching.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a memory cleaning program is stored on the computer-readable storage medium, and when executed by a processor, the memory cleaning program implements the following steps:
when the preset process of the mobile terminal is detected to be blocked, executing a preset processing strategy, and after the preset processing strategy is executed, detecting whether the blocked preset process is recovered to be normal or not;
when the situation that the blocked preset process is not recovered to be normal is detected, acquiring the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the memory of the mobile terminal is abnormal, determining the blocked preset process as a process to be cleaned, and cleaning the memory occupied resources of the process to be cleaned.
Further, when executed by the processor, the memory cleaner further performs the following steps:
reading the memory application information, the memory address information and the memory mapping information of the blocked preset process from the memory operation information;
judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are all preset state values or not;
when the memory application state value, the memory address state value and the memory mapping state value are all preset state values, judging that the memory of the mobile terminal is not abnormal;
and when the memory application state value, the memory address state value and the memory mapping state value are not uniform to be preset state values, judging that the memory of the mobile terminal is abnormal.
Further, when executed by the processor, the memory cleaner further performs the following steps:
monitoring a preset process of the mobile terminal to obtain process monitoring data, and judging whether the preset process is blocked according to the process monitoring data;
and executing the preset processing strategy when the preset process is blocked, and detecting whether the blocked preset process is recovered to be normal or not after the preset processing strategy is executed.
Further, when executed by the processor, the memory cleaner further performs the following steps:
reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set or not;
and when the process state value is not in the preset process state value set, judging that the preset process is blocked.
Further, when executed by the processor, the memory cleaner further performs the following steps:
writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at preset time intervals;
judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
and when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database.
Further, when executed by the processor, the memory cleaner further performs the following steps:
calculating the size of the memory occupied resources of each process to be cleaned, and determining the release sequence of the memory occupied resources of each process to be cleaned according to the size of the memory occupied resources of each process to be cleaned;
and releasing the memory occupied resources of each process to be cleaned according to the release sequence.
Further, when executed by the processor, the memory cleaner further performs the following steps:
when the memory of the mobile terminal is abnormal, obtaining blocking information, and outputting the blocking information and the memory operation information to a feature log file.
The embodiments of the computer-readable storage medium of the present invention are substantially the same as the embodiments of the memory cleaning method described above, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a computer storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (7)
1. A memory cleaning method is characterized in that the memory cleaning method is applied to a mobile terminal, and comprises the following steps:
monitoring a preset process of the mobile terminal to acquire process monitoring data;
reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set or not;
when the process state value is in a preset process state value set, judging that the preset process is blocked, and when the process state value is not in the preset process state value set, judging that the preset process is not blocked;
writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at preset time intervals;
judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database;
when the preset process of the mobile terminal is detected to be blocked, executing a preset processing strategy, and after the preset processing strategy is executed, detecting whether the blocked preset process is recovered to be normal or not;
when the situation that the blocked preset process is not recovered to be normal is detected, acquiring the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the memory of the mobile terminal is abnormal, determining the blocked preset process as a process to be cleaned, and cleaning the memory occupied resources of the process to be cleaned.
2. The method according to claim 1, wherein the step of determining whether the memory of the mobile terminal is abnormal according to the memory operation information comprises:
reading the memory application information, the memory address information and the memory mapping information of the blocked preset process from the memory operation information;
judging whether the memory application state value in the memory application information, the memory address state value in the memory address information and the memory mapping state value in the memory mapping information are all preset state values or not;
when the memory application state value, the memory address state value and the memory mapping state value are all preset state values, judging that the memory of the mobile terminal is not abnormal;
and when the memory application state value, the memory address state value and the memory mapping state value are not uniform to be preset state values, judging that the memory of the mobile terminal is abnormal.
3. The memory cleaning method according to any one of claims 1-2, wherein the step of cleaning the memory occupied resources of the process to be cleaned comprises:
calculating the size of the memory occupied resources of each process to be cleaned, and determining the release sequence of the memory occupied resources of each process to be cleaned according to the size of the memory occupied resources of each process to be cleaned;
and releasing the memory occupied resources of each process to be cleaned according to the release sequence.
4. The method according to any one of claims 1-2, wherein after the step of determining whether the memory of the mobile terminal is abnormal according to the memory operation information, the method further comprises:
when the memory of the mobile terminal is abnormal, obtaining blocking information, and outputting the blocking information and the memory operation information to a feature log file.
5. A mobile terminal, characterized in that the mobile terminal comprises: a memory, a processor, and a memory cleaner stored on the memory and operable on the processor, the memory cleaner when executed by the processor implementing the steps of:
monitoring a preset process of the mobile terminal to acquire process monitoring data;
reading a process state value of the preset process from the process monitoring data, and judging whether the process state value is in a preset process state value set or not;
when the process state value is in a preset process state value set, judging that the preset process is blocked, and when the process state value is not in the preset process state value set, judging that the preset process is not blocked;
writing the process monitoring data into a monitoring database, and reading the process monitoring data from the monitoring database at preset time intervals;
judging whether the process monitoring data is redundant data according to the process state value of the preset process in the process monitoring data;
when the process monitoring data is redundant data, deleting the process monitoring data from the monitoring database;
when the preset process of the mobile terminal is detected to be blocked, executing a preset processing strategy, and after the preset processing strategy is executed, detecting whether the blocked preset process is recovered to be normal or not;
when the situation that the blocked preset process is not recovered to be normal is detected, acquiring the memory operation information of the blocked preset process, and judging whether the memory of the mobile terminal is abnormal or not according to the memory operation information;
when the memory of the mobile terminal is abnormal, determining the blocked preset process as a process to be cleaned, and cleaning the memory occupied resources of the process to be cleaned.
6. The mobile terminal according to claim 5, wherein the memory cleaning program, when executed by the processor, further implements the steps of the memory cleaning method according to any one of claims 1 to 4.
7. A computer-readable storage medium, having a memory scrubbing program stored thereon, which when executed by a processor implements the steps of the memory scrubbing method as recited in any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711247486.9A CN107908478B (en) | 2017-11-30 | 2017-11-30 | Memory cleaning method, mobile terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711247486.9A CN107908478B (en) | 2017-11-30 | 2017-11-30 | Memory cleaning method, mobile terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107908478A CN107908478A (en) | 2018-04-13 |
| CN107908478B true CN107908478B (en) | 2021-11-16 |
Family
ID=61849544
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711247486.9A Active CN107908478B (en) | 2017-11-30 | 2017-11-30 | Memory cleaning method, mobile terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107908478B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108572846B (en) * | 2018-04-24 | 2021-06-25 | 致云科技有限公司 | Software management method and device |
| CN112000470B (en) * | 2020-08-07 | 2024-04-09 | 杭州安恒信息技术股份有限公司 | Memory data processing method, system and device |
| CN112667388B (en) * | 2021-03-16 | 2021-06-01 | 荣耀终端有限公司 | Protection method of operating system and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102117240A (en) * | 2009-12-31 | 2011-07-06 | 腾讯科技（深圳）有限公司 | Method and device for acquiring progress blocking information |
| CN104298612A (en) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | Method and device for cleaning memory in mobile terminal and mobile terminal |
| CN105302637A (en) * | 2015-10-13 | 2016-02-03 | 广东欧珀移动通信有限公司 | Restoration method and apparatus for jamming caused by system process runtime exception and mobile terminal |
| CN107357655A (en) * | 2017-06-22 | 2017-11-17 | 努比亚技术有限公司 | A kind of processing method of process, terminal and computer-readable recording medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8924784B2 (en) * | 2012-04-12 | 2014-12-30 | Freescale Semiconductor, Inc. | Controller for managing a reset of a subset of threads in a multi-thread system |
-
2017
- 2017-11-30 CN CN201711247486.9A patent/CN107908478B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102117240A (en) * | 2009-12-31 | 2011-07-06 | 腾讯科技（深圳）有限公司 | Method and device for acquiring progress blocking information |
| CN104298612A (en) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | Method and device for cleaning memory in mobile terminal and mobile terminal |
| CN105302637A (en) * | 2015-10-13 | 2016-02-03 | 广东欧珀移动通信有限公司 | Restoration method and apparatus for jamming caused by system process runtime exception and mobile terminal |
| CN107357655A (en) * | 2017-06-22 | 2017-11-17 | 努比亚技术有限公司 | A kind of processing method of process, terminal and computer-readable recording medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107908478A (en) | 2018-04-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107861817B (en) | Thread blocking-based memory optimization method, mobile terminal and readable storage medium | |
| CN107678876B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN107807861B (en) | Screen freezing solution method, mobile terminal and computer readable storage medium | |
| CN107590057B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN107704133B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN108052390B (en) | Thread blocking-based memory cleaning method, mobile terminal and readable storage medium | |
| CN107704363B (en) | Screen freezing monitoring method, mobile terminal and computer readable storage medium | |
| CN107807857B (en) | Method and device for cleaning running memory and computer storage medium | |
| CN108073458B (en) | Memory recovery method, mobile terminal and computer-readable storage medium | |
| CN109471690B (en) | Message display method and terminal equipment | |
| CN109040441B (en) | Application body-separating display method, mobile terminal and computer readable storage medium | |
| CN107908492B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107885635B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107766222B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN109522278B (en) | File storage method and terminal equipment | |
| CN107908478B (en) | Memory cleaning method, mobile terminal and computer readable storage medium | |
| CN107704132B (en) | Method for detecting frozen screen of terminal, terminal and computer readable storage medium | |
| CN107967177B (en) | Memory optimization method based on core process, mobile terminal and readable storage medium | |
| CN107908491B (en) | Card screen detection and solution method, mobile terminal and computer readable storage medium | |
| CN107765922B (en) | Card screen detection and solution method, mobile terminal and computer readable storage medium | |
| CN107832191B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107704332B (en) | Screen freezing solution method, mobile terminal and computer readable storage medium | |
| CN107872367B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107818036B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107861826B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |