CN107748632B - Screen freezing monitoring method, mobile terminal and computer readable storage medium - Google Patents
Screen freezing monitoring method, mobile terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN107748632B CN107748632B CN201710903432.7A CN201710903432A CN107748632B CN 107748632 B CN107748632 B CN 107748632B CN 201710903432 A CN201710903432 A CN 201710903432A CN 107748632 B CN107748632 B CN 107748632B
- Authority
- CN
- China
- Prior art keywords
- abnormal
- core library
- base class
- standard interface
- class standard
- 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
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
- G06F3/0416—Control or interface arrangements specially adapted for digitisers
- G06F3/0418—Control or interface arrangements specially adapted for digitisers for error correction or compensation, e.g. based on parallax, calibration or alignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
- G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G3/00—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes
- G09G3/20—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes for presentation of an assembly of a number of characters, e.g. a page, by composing the assembly by combination of individual elements arranged in a matrix no fixed position being assigned to or needed to be assigned to the individual characters or partial characters
- G09G3/34—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes for presentation of an assembly of a number of characters, e.g. a page, by composing the assembly by combination of individual elements arranged in a matrix no fixed position being assigned to or needed to be assigned to the individual characters or partial characters by control of light from an independent source
- G09G3/36—Control arrangements or circuits, of interest only in connection with visual indicators other than cathode-ray tubes for presentation of an assembly of a number of characters, e.g. a page, by composing the assembly by combination of individual elements arranged in a matrix no fixed position being assigned to or needed to be assigned to the individual characters or partial characters by control of light from an independent source using liquid crystals
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Chemical & Material Sciences (AREA)
- Crystallography & Structural Chemistry (AREA)
- Computer Hardware Design (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a frozen screen monitoring method, a mobile terminal and a computer readable storage medium, wherein for the mobile terminal comprising a base class standard interface of a device of each third party manufacturer and a core library depending on the base class standard interface, when the initial loading of the base class standard interface is monitored, whether the core library depending on the base class standard interface is abnormal or not is monitored, and when the core library depending on the base class standard interface is monitored to be abnormal, abnormal data is obtained and output to a characteristic log file. According to the method and the device, when the core library which the base class standard interface depends on is monitored to be abnormal, the abnormal data can be obtained and output to the characteristic log file, and the characteristic log file can be conveniently read when the mobile terminal is frozen, so that the reason for freezing the screen can be quickly positioned, and the labor cost and the time cost are greatly reduced.
Description
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a frozen screen monitoring method, a mobile terminal and a computer readable storage medium.
Background
With the development of mobile terminal technology, more and more Applications (APPs) are integrated in a mobile terminal, and people always encounter a picture freezing problem when using the mobile terminal in daily life, that is, a TP (Touch Panel) and an LCD (Liquid Crystal Display) drive power-on timing sequence and logic are abnormal, for example, a TP cannot be normally powered on and a TP event cannot be reported to a frame due to the fact that the power-on timing sequence and logic driven by the TP and the LCD are abnormal in the process that a user normally uses the mobile terminal, and a Touch screen has no response; that is, the screen loses the focus of the window, for example, the TP can report the touch event normally, but the current window loses the focus, so that the frame layer cannot process the touch event normally, and therefore, the screen is not responded to touch and is frozen.
When the screen is frozen on the mobile terminal, the user generally restarts the mobile terminal to restore the mobile terminal to normal, and when the screen is frozen on the mobile terminal for a long time, the user returns to a manufacturer for maintenance, and needs a developer to position and inquire the reason for the screen to be frozen, so that the mobile terminal can restore to normal. Because the types of the LCD and the TP devices are more, and the realization codes of the devices of different manufacturers are different, when the screen freezing reason is inquired in a positioning mode, more time and labor are consumed to position the screen freezing reason, and the time cost and the labor cost are higher.
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 screen freezing monitoring method, a mobile terminal and a computer readable storage medium, and aims to solve the technical problems that when the screen freezing reason is located and inquired, more time and labor are needed to locate the reason of the screen freezing, and the time cost and the labor cost are higher.
In order to achieve the above object, the present invention provides a freeze-shielding monitoring method, comprising the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface is monitored;
and when monitoring that the core library depended by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
Optionally, the step of monitoring whether an exception occurs in a core library that is depended by the base class standard interface includes:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
Optionally, after the step of acquiring the abnormal data and outputting the abnormal data to the feature log file, the freeze-screen monitoring method further includes:
extracting abnormal core library identification information from the feature log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
Optionally, after the step of acquiring the abnormal data and outputting the abnormal data to the feature log file, the freeze-screen monitoring method further includes:
extracting abnormal memory snapshot data from the feature log file, and acquiring memory snapshot basic data from a local preset database;
comparing the abnormal memory snapshot data with the memory snapshot basic data to obtain the difference degree of the basic data;
and triggering a corresponding exception handling instruction according to the difference degree of the basic data, and executing the exception handling instruction.
Optionally, the step of triggering a corresponding exception handling instruction according to the difference degree of the basic data, and executing the exception handling instruction includes:
judging whether the difference degree of the basic data is greater than or equal to a preset threshold value or not;
if the difference degree of the basic data is larger than or equal to a preset threshold value, triggering a first exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
unloading the abnormal core library in the memory, and reloading the abnormal core library after the abnormal core library is successfully unloaded;
if the difference degree of the basic data is smaller than a preset threshold value, triggering a second exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
releasing the memory used for loading the abnormal core library, and reloading the abnormal core library after the memory is released.
Optionally, the feature log file includes exception core library identification information, exception standard interface information, and exception type information.
In addition, to achieve the above object, the present invention also provides a mobile terminal, including: a memory, a processor, and a freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface is monitored;
and when monitoring that the core library depended by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
The present invention also provides a computer-readable storage medium having a freeze screen monitoring program stored thereon, the freeze screen monitoring program when executed by a processor implementing the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface is monitored;
and when monitoring that the core library depended by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
The invention provides a frozen screen monitoring method, a mobile terminal and a computer readable storage medium, for the mobile terminal comprising a base class standard interface of each third party manufacturer device and a core library depending on the base class standard interface, when the initial loading of the base class standard interface is monitored, whether the core library depending on the base class standard interface is abnormal is monitored, when the core library depending on the base class standard interface is monitored to be abnormal, abnormal data is obtained and output to a characteristic log file, the scheme determines the dependent core library by abstracting and packaging the drive of each third party manufacturer device as the base class standard interface and specifically instantiating the base class standard interface, then when the initial loading of the base class standard interface is monitored, whether the core library depending on the base class standard interface is abnormal is monitored, and when the core library depending on the base class standard interface is monitored to be abnormal, the abnormal data are obtained and output to the characteristic log file, so that when the mobile terminal is frozen, the characteristic log file is read, the reason for freezing the screen is rapidly located, and the labor cost and the time cost are greatly reduced.
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 schematic flow chart of a first embodiment of a freeze screen monitoring method according to the present invention;
FIG. 4 is a schematic flow chart of a second embodiment of a freeze screen monitoring method according to the present invention;
FIG. 5 is a schematic flow chart of a third embodiment of a freeze screen monitoring method according to the present invention;
fig. 6 is a schematic detailed flow chart of the step of triggering the corresponding exception handling instruction according to the difference degree of the basic data and executing the exception handling instruction in fig. 5.
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 freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface is monitored;
and when monitoring that the core library depended by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting abnormal core library identification information from the feature log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting abnormal memory snapshot data from the feature log file, and acquiring memory snapshot basic data from a local preset database;
comparing the abnormal memory snapshot data with the memory snapshot basic data to obtain the difference degree of the basic data;
and triggering a corresponding exception handling instruction according to the difference degree of the basic data, and executing the exception handling instruction.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether the difference degree of the basic data is greater than or equal to a preset threshold value or not;
if the difference degree of the basic data is larger than or equal to a preset threshold value, triggering a first exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
unloading the abnormal core library in the memory, and reloading the abnormal core library after the abnormal core library is successfully unloaded;
if the difference degree of the basic data is smaller than a preset threshold value, triggering a second exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
releasing the memory used for loading the abnormal core library, and reloading the abnormal core library after the memory is released.
Further, the feature log file includes exception core library identification information, exception standard interface information, and exception type information.
The specific embodiment of the mobile terminal of the present invention is substantially the same as the embodiments of the freeze screen monitoring method described below, and will not be described herein again.
Further, the present invention also provides a freeze-screen monitoring 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 freeze-screen monitoring method according to the present invention.
In this embodiment, the freeze screen monitoring method includes:
step S101, when the initialization loading of a base class standard interface is monitored, monitoring whether a core library depended by the base class standard interface is abnormal or not;
the screen freezing monitoring method is applied to a mobile terminal, and the mobile terminal comprises a smart phone, a tablet computer and the like. Because the types of LCD and TP devices are more, the realization codes of devices of different manufacturers are different, developers need to maintain a plurality of sets of codes and need to consider the compatibility of the devices; even if the LCD and TP devices of different models of the same device manufacturer have more differences, in addition, the code coding style and the implementation logic of different device manufacturers have certain differences, great workload is brought to development and maintenance personnel, and problems are easily introduced, so when the freeze screen reasons are inquired in a positioning mode, more time and manpower are consumed to position the reasons for the occurrence of the freeze screen, and the time cost and the labor cost are higher.
Aiming at the problems, developers extract a common part by performing contrastive analysis on the LCD and TP device drivers of different device manufacturers, package the common part into a base class standard interface after adding a custom function, the base class standard interface defines the programming specification and parameter requirement of the interface, then publish the base class standard interface, the programming specification and the parameter requirement to different LCD and TP device manufacturers, the manufacturers develop specific functions on the basis of the base class standard interface, the programming specification and the parameter requirement, when the manufacturers of different LCD and TP devices return to the specific function development realization of the base class standard interface, realize a core library which is depended by the base class standard interface of each manufacturer LCD and TP device, and finally store the core library which is depended by the base class standard interface and the base class standard interface of each manufacturer LCD and TP device into a mobile terminal.
The BSP (Board Support Package) Support of the display part of the operating system is mainly composed of a grafloc (graphics allocation) module of a Hardware Abstraction Layer (HAL) and a Framebuffer driver in an inner core, wherein the grafloc module is located between a general part of a framework layer and the driver of the display device, and is used as a unique interface of the display hardware part to an upper layer. The Gralloc has a place different from other hardware modules, and an operating system must have a Gralloc, otherwise the operating system cannot be started normally. And the default Gralloc module which is realized in the open source code of the operating system is named as Gralloc. It is not only an implementation of an emulator, but also applicable to platforms using standard Framebuffer drivers. So if a specific manufacturer's gradloc.so is used, the default gradloc.default.so of the operating system must be deleted, and both cannot exist at the same time. Based on LCD and TP devices of different device manufacturers, if a specific Gralloc module is realized, the display equipment at the lower layer can be various types of driving programs, namely different LCD and TP device manufacturers can own a set of Gralloc modules, and then the various types of driving programs at the lower layer are connected and called with a frame layer through Gralloc calling of an HAL layer.
When the mobile terminal monitors the initial loading of the base class standard interface, a monitor is created, whether the core library which the base class standard interface depends on is abnormal or not is monitored through the monitor, specifically, whether the base class standard interface which is realized by each specific LCD and TP manufacturer and loaded into the memory has abnormal information which is actively thrown out or not is monitored through the monitor, if the abnormal information which is actively thrown out by the base class standard interface is monitored, the core library which the base class standard interface depends on is abnormal, and if the abnormal information which is actively thrown out by the base class standard interface is not monitored, the core library which the base class standard interface depends on is normal.
Optionally, in this embodiment, the step S101 includes:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
When monitoring the initial loading of a base class standard interface, the mobile terminal monitors whether the memory loading of a core library depended on by the base class standard interface is normal, and when monitoring that the memory loading of the core library depended on by the base class standard interface is normal, the mobile terminal judges that the core library depended on by the base class standard interface is not abnormal; and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
Specifically, if the memory of the core library that the base class standard interface depends on is loaded normally, whether the core library loaded into the memory can be initialized normally is further monitored, if the core library loaded into the memory can be initialized normally, it is determined that the core library that the base class standard interface depends on is not abnormal, and if the core library loaded into the memory cannot be initialized normally, it is determined that the core library that the base class standard interface depends on is abnormal.
And further, if the core library loaded into the memory can be normally initialized, monitoring whether the initialized base class standard interface can be normally called, if the initialized base class standard interface can be normally called, judging that the core library depended on by the base class standard interface is not abnormal, and if the initialized base class standard interface cannot be normally called, judging that the core library depended on by the base class standard interface is abnormal.
Further, if the initialized base class standard interface can be called normally, whether an address error or a pointer error exists when the base class standard interface is called is monitored, if the address error or the pointer error exists when the base class standard interface is called, it is determined that the core library which the base class standard interface depends on is abnormal, and if the address error or the pointer error does not exist when the base class standard interface is called, it is determined that the core library which the base class standard interface depends on is not abnormal.
And step S102, when monitoring that the core library depended on by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
When monitoring that the core library which is depended by the base class standard interface is abnormal, the mobile terminal reports the core library which is depended by the base class standard interface to the framework layer, obtains abnormal data, independently creates a thread to output the abnormal data to a debug process, and the debug process directionally outputs the abnormal data to a feature log file with debug authority processing. The feature file log comprises identification information of the core library with the exception, namely identification information of the core library with the exception, exception standard interface information, exception type information and the like, wherein the exception type information comprises initialization exception of the core library, loading exception of a memory of the core library, memory address error or pointer error during interface calling and the like.
In this embodiment, for a mobile terminal including a base class standard interface of each third-party manufacturer device and a core library depending on the base class standard interface, when it is monitored that the base class standard interface is initially loaded, it is monitored whether the core library depending on the base class standard interface is abnormal, when it is monitored that the core library depending on the base class standard interface is abnormal, abnormal data is obtained and the abnormal data is output to a feature log file, in the present scheme, a driver of each third-party manufacturer device is abstracted and packaged as the base class standard interface, and the base class standard interface is specifically instantiated to determine the core library depending on the base class standard interface, then when it is monitored that the core library depending on the base class standard interface is abnormal, the abnormal data are obtained and output to the characteristic log file, so that when the mobile terminal is frozen, the characteristic log file is read, the reason for freezing the screen is rapidly located, and the labor cost and the time cost are greatly reduced.
Further, referring to fig. 4, a second embodiment of the freeze screen monitoring method according to the present invention is proposed based on the mobile terminal shown in fig. 1 and the first embodiment, and is different from the previous embodiment in that after the step S102, the freeze screen monitoring method further includes:
step S103, extracting abnormal core library identification information from the characteristic log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and step S104, unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
It should be noted that the present invention provides a specific solution for freezing the screen of the mobile terminal based on the foregoing embodiments, and only this will be described below, and other references may be made to the foregoing embodiments.
After the mobile terminal outputs the abnormal data to the feature log file, the abnormal core library identification information is extracted from the feature log file, the corresponding abnormal core library is obtained according to the abnormal core library identification information, then the abnormal core library is unloaded from the mobile terminal memory, and the abnormal core library is reloaded after the abnormal core library is successfully unloaded.
In this embodiment, the core library with the abnormality is acquired through the feature log file, the core library with the abnormality is unloaded in the memory, and the corresponding core library is reloaded after the core library is successfully unloaded, so that a user does not need to return the mobile terminal to a manufacturer for maintenance, the maintenance time is reduced, and the user experience is also improved.
Further, referring to fig. 5, based on the mobile terminal shown in fig. 1 and the first or second embodiment, a third embodiment of the freeze screen monitoring method of the present invention is provided, which is different from the previous embodiment in that after step S102, the freeze screen monitoring method further includes:
step S105, extracting abnormal memory snapshot data from the feature log file, and acquiring memory snapshot basic data from a local preset database;
step S106, comparing the abnormal memory snapshot data with the memory snapshot basic data to obtain the basic data difference degree;
and S107, triggering a corresponding exception handling instruction according to the basic data difference degree, and executing the exception handling instruction.
It should be noted that the present invention proposes another solution for the frozen screen of the mobile terminal based on the foregoing embodiments, and only this will be described below, and other references may be made to the foregoing embodiments.
When the LCD and the TP are initialized and normally work, the mobile terminal obtains the memory snapshot basic data, the memory snapshot basic data comprise basic information such as the loaded core library identification, the object name and the number contained in the core library, the core library version number and the like, and the memory snapshot basic data are stored in a local preset database.
After outputting the abnormal data to the feature log file, the mobile terminal extracts the abnormal memory snapshot data from the feature log file, acquires the memory snapshot basic data from a local preset database, compares the abnormal memory snapshot data with the memory snapshot basic data to acquire the basic data difference degree, finally triggers the corresponding abnormal processing instruction according to the basic data difference degree, and executes the abnormal processing instruction.
Specifically, referring to fig. 6, fig. 6 is a detailed flowchart of step S107 in fig. 5, where step S107 includes:
step S1071, judge whether the said basic data difference degree is greater than or equal to the predetermined threshold;
step S1072, if the difference degree of the basic data is greater than or equal to a preset threshold value, triggering a first exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
step S1073, uninstall the said abnormal core storehouse in the memory, and reload the said abnormal core storehouse after uninstalling the said abnormal core storehouse successfully;
step S1074, if the difference degree of the basic data is smaller than a preset threshold value, triggering a second exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
step S1075, releasing the memory used for loading the abnormal core library, and reloading the abnormal core library after the memory is released.
The mobile terminal compares the abnormal memory snapshot data with the memory snapshot basic data to obtain a basic data difference degree, then judges whether the basic data difference degree is larger than or equal to a preset threshold value, if the basic data difference degree is larger than or equal to the preset threshold value, the memory snapshot basic data difference of the abnormal memory snapshot data is larger, therefore, a first abnormal processing instruction is triggered, an abnormal core library is determined according to the first abnormal processing instruction and the characteristic log file, then the abnormal core library is unloaded in a memory, and the abnormal core library is reloaded after the abnormal core library is successfully unloaded; if the basic data difference degree is smaller than a preset threshold value, the memory snapshot basic data difference of the abnormal memory snapshot data is smaller, therefore, a second abnormal processing instruction is triggered, an abnormal core library is determined according to the first abnormal processing instruction and the characteristic log file, then the memory used for loading the abnormal core library is released, and the abnormal core library is reloaded after the memory is released.
In a specific implementation, when the difference degree of the basic data is low, an exception handling instruction is further triggered according to a preset decision condition, and the exception handling instruction is executed, where the preset decision condition includes whether an address read from a memory is incorrect, whether an internal execution time is overtime, whether an exception occurs during initialization, and a corresponding method cannot be found during execution, and when the difference degree of the basic data is zero, a method in an exception core library is tried to be re-executed for a preset number of times, and a preset number of times of calling is not necessarily required to be re-executed, and the logic is skipped as long as there is a correct execution in the calling.
In this embodiment, the abnormal memory snapshot data in the feature log file is compared with the memory snapshot basic data in the local preset database, and different exception handling instructions are triggered and executed according to the difference degree of the basic data between the abnormal memory snapshot data and the memory snapshot basic data, so that specific exception conditions and specific handling are realized, accuracy of exception handling is greatly guaranteed, a user does not need to return the mobile terminal to a manufacturer for maintenance, maintenance time is reduced, and user experience is improved.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a freeze-screen monitoring program is stored on the computer-readable storage medium, and when executed by a processor, the freeze-screen monitoring program implements the following steps:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface is monitored;
and when monitoring that the core library depended by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting abnormal core library identification information from the feature log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting abnormal memory snapshot data from the feature log file, and acquiring memory snapshot basic data from a local preset database;
comparing the abnormal memory snapshot data with the memory snapshot basic data to obtain the difference degree of the basic data;
and triggering a corresponding exception handling instruction according to the difference degree of the basic data, and executing the exception handling instruction.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether the difference degree of the basic data is greater than or equal to a preset threshold value or not;
if the difference degree of the basic data is larger than or equal to a preset threshold value, triggering a first exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
unloading the abnormal core library in the memory, and reloading the abnormal core library after the abnormal core library is successfully unloaded;
if the difference degree of the basic data is smaller than a preset threshold value, triggering a second exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
releasing the memory used for loading the abnormal core library, and reloading the abnormal core library after the memory is released.
Further, the feature log file includes exception core library identification information, exception standard interface information, and exception type information.
The specific embodiment of the computer-readable storage medium of the present invention is substantially the same as the specific embodiments of the freeze screen monitoring method described above, and will not be 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 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 (8)
1. A screen freezing monitoring method is applied to a mobile terminal and comprises the following steps:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface of the LCD and TP devices is monitored;
when monitoring that the core library depended on by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file;
the base class standard interfaces of the LCD and TP devices are predefined with the programming specification and parameter requirements of the interfaces;
the step of monitoring whether the core library depended by the base class standard interface is abnormal or not comprises the following steps:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
2. The freeze monitoring method of claim 1, wherein after the step of obtaining the anomaly data and outputting the anomaly data to a signature log file, the freeze monitoring method further comprises:
extracting abnormal core library identification information from the feature log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
3. The freeze monitoring method of any of claims 1-2, wherein after the step of obtaining the anomaly data and outputting the anomaly data to a signature log file, the freeze monitoring method further comprises:
extracting abnormal memory snapshot data from the feature log file, and acquiring memory snapshot basic data from a local preset database;
comparing the abnormal memory snapshot data with the memory snapshot basic data to obtain the difference degree of the basic data;
and triggering a corresponding exception handling instruction according to the difference degree of the basic data, and executing the exception handling instruction.
4. A freeze screen monitoring method as claimed in claim 3 wherein the step of triggering a corresponding exception handling instruction according to the degree of difference in the base data and executing the exception handling instruction comprises:
judging whether the difference degree of the basic data is greater than or equal to a preset threshold value or not;
if the difference degree of the basic data is larger than or equal to a preset threshold value, triggering a first exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
unloading the abnormal core library in the memory, and reloading the abnormal core library after the abnormal core library is successfully unloaded;
if the difference degree of the basic data is smaller than a preset threshold value, triggering a second exception handling instruction, and determining an exception core library according to the first exception handling instruction and the feature log file;
releasing the memory used for loading the abnormal core library, and reloading the abnormal core library after the memory is released.
5. The freeze screen monitoring method of claim 1, wherein the profile log file includes anomaly core library identification information, anomaly standard interface information, and anomaly type information.
6. A mobile terminal, characterized in that the mobile terminal comprises: a memory, a processor, and a freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface of the LCD and TP devices is monitored;
when monitoring that the core library depended on by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file;
the base class standard interfaces of the LCD and TP devices are predefined with the programming specification and parameter requirements of the interfaces;
the step of monitoring whether the core library depended by the base class standard interface is abnormal or not comprises the following steps:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
7. The mobile terminal of claim 6, wherein the freeze monitor program, when executed by the processor, further performs the steps of:
extracting abnormal core library identification information from the feature log file, and acquiring a corresponding abnormal core library according to the abnormal core library identification information;
and unloading the abnormal core library in the memory, and reloading the abnormal core library after successful unloading.
8. A computer-readable storage medium having a freeze screen monitoring program stored thereon, the freeze screen monitoring program when executed by a processor implementing the steps of:
monitoring whether a core library depended by a base class standard interface is abnormal or not when the initialization loading of the base class standard interface of the LCD and TP devices is monitored;
when monitoring that the core library depended on by the base class standard interface is abnormal, acquiring abnormal data and outputting the abnormal data to a feature log file;
the base class standard interfaces of the LCD and TP devices are predefined with the programming specification and parameter requirements of the interfaces;
the step of monitoring whether the core library depended by the base class standard interface is abnormal or not comprises the following steps:
when the initialization loading of a base class standard interface is monitored, monitoring whether the memory loading of a core library depended by the base class standard interface is normal or not;
when the memory loading of the core library which the base class standard interface depends on is monitored to be normal, judging that the core library which the base class standard interface depends on is not abnormal;
and when the abnormal memory loading of the core library depended on by the base class standard interface is monitored, judging that the core library depended on by the base class standard interface is abnormal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710903432.7A CN107748632B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710903432.7A CN107748632B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107748632A CN107748632A (en) | 2018-03-02 |
| CN107748632B true CN107748632B (en) | 2021-11-02 |
Family
ID=61254596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710903432.7A Active CN107748632B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107748632B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115016665B (en) * | 2021-09-14 | 2023-04-21 | 北京荣耀终端有限公司 | Frozen screen fault detection method, electronic equipment and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101652747A (en) * | 2007-03-29 | 2010-02-17 | 微软公司 | Parallel dll tree initialization |
| CN101840352A (en) * | 2010-04-29 | 2010-09-22 | 中兴通讯股份有限公司 | Method and device for monitoring database connection pool |
| CN107168773A (en) * | 2017-06-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Positioning problems and the processing method and processing device of application recovery after a kind of JVM collapses |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8938722B2 (en) * | 2012-10-17 | 2015-01-20 | International Business Machines Corporation | Identifying errors using context based class names |
-
2017
- 2017-09-28 CN CN201710903432.7A patent/CN107748632B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101652747A (en) * | 2007-03-29 | 2010-02-17 | 微软公司 | Parallel dll tree initialization |
| CN101840352A (en) * | 2010-04-29 | 2010-09-22 | 中兴通讯股份有限公司 | Method and device for monitoring database connection pool |
| CN107168773A (en) * | 2017-06-12 | 2017-09-15 | 郑州云海信息技术有限公司 | Positioning problems and the processing method and processing device of application recovery after a kind of JVM collapses |
Non-Patent Citations (1)
| Title |
|---|
| 虚拟化平台操作系统内核级Rootkits防护方法研究;闫广禄;《中国博士学位论文全文数据库 信息科技辑》;20160715;I138-7 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107748632A (en) | 2018-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107276789B (en) | Log uploading method and device and computer 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 | |
| CN107861817B (en) | Thread blocking-based memory optimization method, mobile terminal and readable storage medium | |
| CN107704332B (en) | Screen freezing solution method, mobile terminal and computer readable storage medium | |
| CN107704133B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN107885635B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107704363B (en) | Screen freezing monitoring method, mobile terminal and computer 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 | |
| CN109964227A (en) | Update the method and terminal of SELinux security strategy | |
| CN107766222B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107908492B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN108052430B (en) | Mobile terminal restart positioning method, mobile terminal and computer readable storage medium | |
| CN107967177B (en) | Memory optimization method based on core process, mobile terminal and readable storage medium | |
| CN111124753A (en) | Application program control method, electronic equipment and server | |
| CN107861827B (en) | Card screen detection method, mobile terminal and computer readable storage medium | |
| CN107832191B (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 | |
| CN107818036B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107872367B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN109828770B (en) | Software upgrading method, terminal equipment and server | |
| CN107748633B (en) | Solution for terminal screen freezing, terminal and computer readable storage medium | |
| CN107908478B (en) | Memory cleaning 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 |