CN108089935B - Application program management method and mobile terminal - Google Patents
Application program management method and mobile terminal Download PDFInfo
- Publication number
- CN108089935B CN108089935B CN201711230873.1A CN201711230873A CN108089935B CN 108089935 B CN108089935 B CN 108089935B CN 201711230873 A CN201711230873 A CN 201711230873A CN 108089935 B CN108089935 B CN 108089935B
- Authority
- CN
- China
- Prior art keywords
- application program
- functional module
- module
- modules
- judgment result
- 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
- 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/0715—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 a system implementing multitasking
-
- 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/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides an application program management method and a mobile terminal, wherein the method comprises the following steps: collecting running state parameters of an application program; determining whether the application program is abnormal or not according to the running state parameters; and when the application program is determined to be abnormal, managing the thread and/or the functional module which are/is currently operated by the application program. According to the embodiment of the invention, the application program is effectively managed according to the running state parameters of the application program, so that the application program can keep quick response, and the stability of the application program is improved.
Description
Technical Field
The present invention relates to the field of mobile terminal technologies, and in particular, to a management method for an application program and a mobile terminal.
Background
At present, the mobile terminal becomes an indispensable communication and entertainment tool in daily life of people. The mobile terminal can be provided with application programs with various functions, and the installed application programs bring great convenience to daily life and work of users.
At present, the longer the application program is, the more easily the problems of blocking or false death and the like occur, and the use experience of a user is greatly influenced. The existing solution is as follows: and managing a memory and reducing main thread operation in the static coding stage of the application program. Although most of application program performance problems can be solved by the existing static coding adjusting mode, along with more and more application program functions, the coding structure of the application program is more and more complex, the problem of the application program performance is more and more complicated to solve by the static coding adjusting mode, and the performance problem of static checking is more and more incomplete. Therefore, the existing scheme for solving the performance problem of the application program in the static coding stage cannot effectively solve the performance problem of the application program in the operation.
Disclosure of Invention
The embodiment of the invention provides an application program management method and a mobile terminal, and aims to solve the performance problem of an application program in operation.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, a method for managing an application program is provided, where the method is applied to a mobile terminal, and includes: collecting running state parameters of an application program; determining whether the application program is abnormal or not according to the running state parameters; and when the application program is determined to be abnormal, managing the thread and/or the functional module which are/is currently operated by the application program.
In a second aspect, a mobile terminal is provided, including: the acquisition module is used for acquiring the running state parameters of the application program; the determining module is used for determining whether the application program is abnormal or not according to the running state parameters; and the management module is used for managing the thread and/or the functional module which is currently operated by the application program when the application program is determined to be abnormal.
In a third aspect, a mobile terminal is provided, including: memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the management method of an application.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method for managing an application.
Compared with the prior art, the invention has the following advantages:
in the embodiment of the invention, the application program is effectively managed according to the running state parameters of the application program, so that the application program can keep quick response, and the stability of the application program is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating steps of a method for managing an application according to a first embodiment of the present invention;
FIG. 2 is a flowchart illustrating steps of a method for managing application programs according to a second embodiment of the present invention;
FIG. 3 is a tree of structures between functional modules of an application;
fig. 4 is a block diagram of a mobile terminal according to a third embodiment of the present invention;
fig. 5 is a schematic diagram of a hardware structure of a mobile terminal according to a fourth embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, a flowchart illustrating steps of a method for managing an application according to a first embodiment of the present invention is shown.
The management method of the application program of the embodiment of the invention comprises the following steps:
step 101: and collecting the running state parameters of the application program.
Wherein, the operation state parameters may include: at least one of the memory value, the number of running processes, the number of open modules and the frame refreshing frequency is occupied. In the specific implementation process, the specific setting of the operating state parameter can be selectively set by a person skilled in the art according to actual requirements.
Step 102: and determining whether the application program is abnormal or not according to the running state parameters.
The mobile terminal is preset with threshold values corresponding to the state parameters, and when one or more running state parameter values exceed the corresponding threshold values, the application program is determined to be abnormal.
Step 103: and when the application program is determined to be abnormal, managing the thread and/or the functional module which are/is currently operated by the application program.
The application program is provided with a plurality of threads and a plurality of functional modules, each functional module corresponds to one function, each functional module needs to occupy a certain memory after being started, and the running threads also need to occupy the resources of the mobile terminal. In the embodiment of the invention, when the application program is determined to be abnormal, the currently running thread and the currently running functional module are managed so as to release the resources occupied by the running process or the currently running functional module, thereby improving the response speed of the application program.
Specifically, only the currently running thread or only the currently running functional module may be managed during management; threads and functional modules can also be managed simultaneously.
According to the management method of the application program, provided by the embodiment of the invention, the running state parameters of the application program are collected in the running process of the application program, whether the application program is abnormal or not is determined according to the running state parameters, and when the application program is abnormal, the currently running thread and/or functional module of the application program are managed, so that the performance problem of the application program can be dynamically and effectively managed, and the use experience of a user is improved. The application program management method provided by the embodiment of the invention can be suitable for each installed application program by only setting one set of management program in the mobile terminal, has good universality compared with the existing static codes for respectively adjusting each application program, and can reduce the workload of application program developers.
Example two
Referring to fig. 2, a flowchart illustrating steps of a method for managing an application according to a second embodiment of the present invention is shown.
The management method of the application program of the embodiment of the invention specifically comprises the following steps:
step 201: and collecting the running state parameters of the application program.
Wherein, the operation state parameters may include: at least one of the memory value, the number of running processes, the number of open modules and the frame refreshing frequency is occupied.
And after the application program is started, registering an application program management module, wherein the application program management module is internally provided with the application program management program, and managing the application program through the application program management program. In the running process of the application program, the application program management program monitors the running state of the application program and collects running state parameters.
Step 202: and determining whether the application program is abnormal or not according to the running state parameters.
The embodiment of the invention adopts the following operating state parameters: the occupied memory value, the number of running processes, the number of starting modules and the frame refreshing frequency are taken as examples for explanation. One way to determine whether an application is anomalous, preferably in dependence on the operating state parameters, is as follows:
judging whether the occupied memory value is larger than a preset memory threshold value or not to obtain a first judgment result;
judging whether the number of the running processes is larger than the preset number of the processes or not to obtain a second judgment result;
judging whether the number of the starting modules is larger than the number of the preset modules or not to obtain a third judgment result;
judging whether the picture refreshing frequency is lower than a preset frequency or not to obtain a fourth judgment result;
and when at least one of the first judgment result, the second judgment result, the third judgment result and the fourth judgment result is yes, determining that the application program is abnormal. Correspondingly, if the four judgment results are negative, determining that the application program is not abnormal.
Step 203: and when the application program is determined to be abnormal, determining the first function module pointed by the function pointer.
After the application registration is completed, the application management module generates a functional module structure tree for the registered application, as shown in fig. 3. As can be seen from fig. 3, the application program includes a main interface function module, the main interface function module can start the downloading function module and the comment function module, the comment function module can start the sharing function module, and the downloading function module can start the uploading function module. That is, only the downloading or comment function can be started after the main interface is opened, the analysis function can be started after the comment function is opened, and the uploading function can be started after the downloading function is opened.
Wherein, an application corresponds to a function pointer, and the function module pointed by the function pointer is a function module operated by the foreground, for example: and if the comment is opened currently, the function module pointed by the function pointer is the comment function module.
Step 204: and searching a function module set of which the path length between the function module and the first function module is less than or equal to a preset value.
The functional module with the path length between the first functional module and the second functional module being smaller than or equal to the preset value is a functional module which can be started by the first functional module.
For example: as shown in fig. 4, the preset value is 1, and the function modules having a path length less than or equal to 1 with the main interface function module are a download function module and a comment function module.
Step 205: and setting the currently running functional modules except the functional module set and the first functional module into a dormant state.
The determined function module set is kept in an opening state, so that the call to a certain module in the function module set can be responded quickly, and the time consumed for opening the module is saved.
And setting the currently running functional modules except the functional module set and the first functional module into a dormant state to release the memory resources occupied by the functional modules.
one way of preferably managing the currently running functional modules is as follows:
firstly, determining a first function module pointed by a function pointer;
secondly, determining the path length between each currently running functional module and the first functional module;
the path length between the first function module and each currently running function module can be determined through the function module structure tree corresponding to the application program. For example: the first function module is a main interface function module, the path length between the downloading function module and the first function module is 1, and the path length between the uploading function module and the first function module is 2.
And thirdly, closing the functional modules one by one according to the rule of the path from far to near until the running state of the application program is recovered to be normal.
And in the process of closing the functional module, the application program management module acquires the running state parameters of the application program in real time and judges whether the running state of the application program is recovered to be normal or not.
One way to preferably manage the threads currently running by the application is as follows:
firstly, determining a first function module pointed by a function pointer;
secondly, determining an interface thread corresponding to the first functional module;
and finally, adjusting the priority of the interface thread to be the highest.
In the embodiment of the present invention, Interface threads of other functional modules and priority of a task in a queue of the CUI threads are reduced, and the priority of the Interface thread of the first functional module is adjusted to be the highest, so as to ensure that the first functional module executes quickly.
The method for managing the application program provided by the embodiment of the invention has the beneficial effects of the method for managing the application program in the first embodiment, and also provides a preferable mode for managing the currently running thread and/or function module, so that the currently running function module can be ensured to be quickly responded, and the function module to be used later can be ensured to be quickly called, thereby improving the response speed of the application program.
EXAMPLE III
Referring to fig. 4, a block diagram of a mobile terminal according to a third embodiment of the present invention is shown.
The mobile terminal of the embodiment of the invention can comprise:
the acquisition module 301 is used for acquiring the running state parameters of the application program;
a determining module 302, configured to determine whether an exception occurs in the application according to the running state parameter;
the management module 303 is configured to manage a currently running thread and/or function module of the application program when it is determined that the application program is abnormal.
Preferably, the operating state parameters include: at least one of the memory value, the number of running processes, the number of open modules and the frame refreshing frequency is occupied.
Preferably, the determining module 302 may include:
a first determining submodule 3021, configured to determine, when the operation state parameter includes an occupied memory value, an operation process number, a starting module number, and a picture refresh frequency, whether the occupied memory value is greater than a preset memory threshold value, so as to obtain a first determination result;
a second determining submodule 3022, configured to determine whether the number of running processes is greater than a preset number of processes, to obtain a second determination result;
a third determining submodule 3023, configured to determine whether the number of the starting modules is greater than a preset number of modules, to obtain a third determination result;
a fourth determining submodule 3024, configured to determine whether the picture refreshing frequency is lower than a preset frequency, to obtain a fourth determination result;
a result determining submodule 3025, configured to determine that the application program is abnormal when at least one of the first determination result, the second determination result, the third determination result, and the fourth determination result is yes.
Preferably, the management module 303 may include:
a first determining submodule 3031, configured to determine a first function module pointed by the function pointer;
the searching submodule 3032 is configured to search a function module set, of which the path length with the first function module is smaller than or equal to a preset value;
a first closing submodule 3033, configured to set currently-operating functional modules, other than the functional module set and the first functional module, to a sleep state.
Preferably, the management module 303 may include:
a second determining submodule 3034, configured to determine the first function module pointed by the function pointer;
a path determining submodule 3035, configured to determine paths between the currently running functional modules and the first functional module;
and a second closing submodule 3036, configured to close the function modules one by one according to a rule that a path is from far to near until the running state of the application program returns to normal.
Preferably, the management module 303 includes:
a third determining submodule 3037, configured to determine the first function module pointed by the function pointer;
the thread determining submodule 3038 is configured to determine an interface thread corresponding to the first functional module;
and an adjusting submodule 3039, configured to adjust the priority of the interface thread to be highest.
The mobile terminal provided in the embodiment of the present invention can implement each process implemented by the mobile terminal in the method embodiments of fig. 1 to fig. 3, and is not described herein again to avoid repetition.
According to the mobile terminal provided by the embodiment of the invention, the running state parameters of the application program are collected in the running process of the application program, whether the application program is abnormal or not is determined according to the running state parameters, and when the application program is abnormal, the currently running thread and/or functional module of the application program are managed, so that the performance problem of the application program can be dynamically and effectively managed, and the use experience of a user is improved. The mobile terminal provided by the embodiment of the invention can be suitable for each installed application program by only setting one set of management program in the mobile terminal, has good universality compared with the existing static codes for respectively adjusting each application program, and can reduce the workload of application program developers.
Example four
Figure 5 is a schematic diagram of a hardware configuration of a mobile terminal implementing various embodiments of the present invention,
the mobile terminal 400 includes, but is not limited to: radio frequency unit 401, network module 402, audio output unit 403, input unit 404, sensor 405, display unit 406, user input unit 407, interface unit 408, memory 409, processor 410, and power supply 411. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 5 is not intended to be limiting of mobile terminals, and that a mobile terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the mobile terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.
The processor 410 is configured to collect an operation state parameter of an application program; determining whether the application program is abnormal or not according to the running state parameters; and when the application program is determined to be abnormal, managing the thread and/or the functional module which are/is currently operated by the application program.
According to the mobile terminal provided by the embodiment of the invention, the application program is effectively managed according to the running state parameters of the application program, so that the application program can keep quick response, and the stability of the application program is improved.
It should be understood that, in the embodiment of the present invention, the radio frequency unit 401 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 410; in addition, the uplink data is transmitted to the base station. Typically, radio unit 401 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. Further, the radio unit 401 can also communicate with a network and other devices through a wireless communication system.
The mobile terminal provides the user with wireless broadband internet access through the network module 402, such as helping the user send and receive e-mails, browse web pages, and access streaming media.
The audio output unit 403 may convert audio data received by the radio frequency unit 401 or the network module 402 or stored in the memory 409 into an audio signal and output as sound. Also, the audio output unit 403 may also provide audio output related to a specific function performed by the mobile terminal 400 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 403 includes a speaker, a buzzer, a receiver, and the like.
The input unit 404 is used to receive audio or video signals. The input Unit 404 may include a Graphics Processing Unit (GPU) 4041 and a microphone 4042, and the Graphics processor 4041 processes image data of a still picture or video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 406. The image frames processed by the graphic processor 4041 may be stored in the memory 409 (or other storage medium) or transmitted via the radio frequency unit 401 or the network module 402. The microphone 4042 may receive sound, and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 401 in case of the phone call mode.
The mobile terminal 400 also includes at least one sensor 405, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 4061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 4061 and/or the backlight when the mobile terminal 400 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), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of the mobile terminal (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 405 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be described in detail herein.
The display unit 406 is used to display information input by the user or information provided to the user. The Display unit 406 may include a Display panel 4061, and the Display panel 4061 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 407 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 407 includes a touch panel 4071 and other input devices 4072. Touch panel 4071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 4071 using a finger, a stylus, or any suitable object or attachment). The touch panel 4071 may include two parts, 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 410, receives a command from the processor 410, and executes the command. In addition, the touch panel 4071 can be implemented by using various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 4071, the user input unit 407 may include other input devices 4072. Specifically, the other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein again.
Further, the touch panel 4071 can be overlaid on the display panel 4061, and when the touch panel 4071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 410 to determine the type of the touch event, and then the processor 410 provides a corresponding visual output on the display panel 4061 according to the type of the touch event. Although in fig. 4, the touch panel 4071 and the display panel 4061 are two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 4071 and the display panel 4061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited herein.
The interface unit 408 is an interface through which an external device is connected to the mobile terminal 400. 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 408 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 400 or may be used to transmit data between the mobile terminal 400 and external devices.
The memory 409 may be used to store software programs as well as various data. The memory 409 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 409 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.
The processor 410 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 409 and calling data stored in the memory 409, thereby integrally monitoring the mobile terminal. Processor 410 may include one or more processing units; preferably, the processor 410 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 410.
The mobile terminal 400 may further include a power supply 411 (e.g., a battery) for supplying power to various components, and preferably, the power supply 411 may be logically connected to the processor 410 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.
In addition, the mobile terminal 400 includes some functional modules that are not shown, and thus, are not described in detail herein.
Preferably, an embodiment of the present invention further provides a mobile terminal, which includes a processor 410, a memory 409, and a computer program that is stored in the memory 409 and can be run on the processor 410, and when being executed by the processor 410, the computer program implements each process of the management method embodiment of the application program, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the management method embodiment of the application program, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
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 apparatus 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 apparatus. 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 apparatus that comprises the element.
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 solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as 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.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (8)
1. A management method of an application program is applied to a mobile terminal, and is characterized by comprising the following steps:
collecting running state parameters of an application program;
determining whether the application program is abnormal or not according to the running state parameters;
when the application program is determined to be abnormal, managing a thread and/or a functional module which is currently operated by the application program;
the managing the thread and/or the functional module currently running by the application program comprises:
determining a first function module pointed by a function pointer, wherein the first function module points to a function module operated in the foreground;
searching a functional module set of which the path length between the functional module set and the first functional module is smaller than or equal to a preset value; wherein the path length represents the number of levels between other modules and the first functional module, the other modules being functional modules that the first functional module can launch;
and setting the currently running functional modules except the functional module set and the first functional module into a dormant state.
2. The method of claim 1, wherein the operating state parameters comprise: at least one of the memory value, the number of running processes, the number of open modules and the frame refreshing frequency is occupied.
3. The method of claim 1, wherein when the operating state parameter comprises: when the memory value, the number of running processes, the number of starting modules and the picture refreshing frequency are occupied, the step of determining whether the application program is abnormal according to the running state parameters comprises the following steps:
judging whether the occupied memory value is larger than a preset memory threshold value or not to obtain a first judgment result;
judging whether the number of the running processes is larger than the preset number of the processes or not to obtain a second judgment result;
judging whether the number of the starting modules is larger than the number of the preset modules or not to obtain a third judgment result;
judging whether the picture refreshing frequency is lower than a preset frequency or not to obtain a fourth judgment result;
and when at least one of the first judgment result, the second judgment result, the third judgment result and the fourth judgment result is yes, determining that the application program is abnormal.
4. A mobile terminal, characterized in that the mobile terminal comprises:
the acquisition module is used for acquiring the running state parameters of the application program;
the determining module is used for determining whether the application program is abnormal or not according to the running state parameters;
the management module is used for managing the thread and/or the functional module which is currently operated by the application program when the application program is determined to be abnormal;
the management module comprises:
the first determining submodule is used for determining a first functional module pointed by the function pointer, and the first functional module is a functional module operated in the foreground;
the searching submodule is used for searching a functional module set of which the path length between the searching submodule and the first functional module is less than or equal to a preset value; wherein the path length represents the number of levels between other modules and the first functional module, the other modules being functional modules that the first functional module can launch;
and the first closing submodule is used for setting the currently running functional modules except the functional module set and the first functional module into a dormant state.
5. The mobile terminal of claim 4, wherein the operating state parameters comprise: at least one of the memory value, the number of running processes, the number of open modules and the frame refreshing frequency is occupied.
6. The mobile terminal of claim 5, wherein the determining module comprises:
the first judgment submodule is used for judging whether the occupied memory value is greater than a preset memory threshold value or not when the running state parameters comprise the occupied memory value, the running process number, the starting module number and the picture refreshing frequency, so as to obtain a first judgment result;
the second judgment submodule is used for judging whether the number of the running processes is larger than the preset number of the processes or not to obtain a second judgment result;
the third judgment submodule is used for judging whether the number of the starting modules is larger than the number of the preset modules or not to obtain a third judgment result;
the fourth judgment submodule is used for judging whether the picture refreshing frequency is lower than the preset frequency or not to obtain a fourth judgment result;
and the result determining submodule is used for determining that the application program is abnormal when at least one of the first judgment result, the second judgment result, the third judgment result and the fourth judgment result is yes.
7. A mobile terminal, characterized in that it comprises a processor, a memory and a computer program stored on said memory and executable on said processor, said computer program, when executed by said processor, implementing the steps of the management method of an application program according to any one of claims 1 to 3.
8. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the management method of an application program according to any one of claims 1 to 3.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711230873.1A CN108089935B (en) | 2017-11-29 | 2017-11-29 | Application program management method and mobile terminal |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711230873.1A CN108089935B (en) | 2017-11-29 | 2017-11-29 | Application program management method and mobile terminal |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108089935A CN108089935A (en) | 2018-05-29 |
CN108089935B true CN108089935B (en) | 2021-04-09 |
Family
ID=62173441
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201711230873.1A Active CN108089935B (en) | 2017-11-29 | 2017-11-29 | Application program management method and mobile terminal |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108089935B (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109587345B (en) * | 2018-12-28 | 2021-09-07 | 努比亚技术有限公司 | Abnormal application prompting method, mobile terminal and computer readable storage medium |
CN111897600A (en) * | 2020-07-31 | 2020-11-06 | 惠州Tcl移动通信有限公司 | Method, device, mobile terminal and system for reducing application memory occupation |
CN114721742A (en) * | 2022-04-14 | 2022-07-08 | 北京字节跳动网络技术有限公司 | Application program starting optimization method and device, computer equipment and storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104317649A (en) * | 2014-09-30 | 2015-01-28 | 北京金山安全软件有限公司 | Processing method and device of terminal application program APP and terminal |
CN104714874A (en) * | 2015-02-28 | 2015-06-17 | 深圳市中兴移动通信有限公司 | Method for intelligently optimizing internal storage of mobile terminal and mobile terminal |
CN105786571A (en) * | 2016-02-29 | 2016-07-20 | 珠海市魅族科技有限公司 | Mobile terminal and control method thereof |
CN106502785A (en) * | 2016-09-30 | 2017-03-15 | 维沃移动通信有限公司 | A kind of cleaning internal memory method and device of mobile terminal |
CN107402804A (en) * | 2017-07-31 | 2017-11-28 | 广东欧珀移动通信有限公司 | Background process management-control method, device, storage medium and electronic equipment |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050216241A1 (en) * | 2004-03-29 | 2005-09-29 | Gadi Entin | Method and apparatus for gathering statistical measures |
CN104102540B (en) * | 2014-06-30 | 2017-08-25 | 上海卓悠网络科技有限公司 | The management method and mobile terminal of a kind of operation process |
CN106802935B (en) * | 2016-12-29 | 2020-08-04 | 腾讯科技(深圳)有限公司 | Page fluency testing method and device |
-
2017
- 2017-11-29 CN CN201711230873.1A patent/CN108089935B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104317649A (en) * | 2014-09-30 | 2015-01-28 | 北京金山安全软件有限公司 | Processing method and device of terminal application program APP and terminal |
CN104714874A (en) * | 2015-02-28 | 2015-06-17 | 深圳市中兴移动通信有限公司 | Method for intelligently optimizing internal storage of mobile terminal and mobile terminal |
CN105786571A (en) * | 2016-02-29 | 2016-07-20 | 珠海市魅族科技有限公司 | Mobile terminal and control method thereof |
CN106502785A (en) * | 2016-09-30 | 2017-03-15 | 维沃移动通信有限公司 | A kind of cleaning internal memory method and device of mobile terminal |
CN107402804A (en) * | 2017-07-31 | 2017-11-28 | 广东欧珀移动通信有限公司 | Background process management-control method, device, storage medium and electronic equipment |
Also Published As
Publication number | Publication date |
---|---|
CN108089935A (en) | 2018-05-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111049979B (en) | Application sharing method, electronic equipment and computer readable storage medium | |
US11366510B2 (en) | Processing method for reducing power consumption and mobile terminal | |
CN107734175B (en) | Notification message prompting method and mobile terminal | |
CN108135033B (en) | Bluetooth connection method and mobile terminal | |
CN110837327B (en) | Message viewing method and terminal | |
CN108322599B (en) | Network access method and mobile terminal | |
CN109739429B (en) | Screen switching processing method and mobile terminal equipment | |
CN108984066B (en) | Application icon display method and mobile terminal | |
CN109343788B (en) | Operation control method of mobile terminal and mobile terminal | |
CN107734170B (en) | Notification message processing method, mobile terminal and wearable device | |
CN109284144B (en) | Fast application processing method and mobile terminal | |
CN109558046B (en) | Information display method and terminal equipment | |
CN107977113B (en) | Control method and mobile terminal | |
CN110569119A (en) | Background application program management method and terminal | |
CN111061404A (en) | Control method and first electronic device | |
CN108008892B (en) | Function starting method and terminal | |
CN108388400B (en) | Operation processing method and mobile terminal | |
CN108089935B (en) | Application program management method and mobile terminal | |
CN107729100B (en) | Interface display control method and mobile terminal | |
CN111124098A (en) | Intelligent power saving method and device for terminal and readable storage medium | |
CN109739430B (en) | Display method and mobile terminal | |
CN109947617B (en) | Method, terminal and readable storage medium for monitoring display content of application interface | |
CN108170360B (en) | Control method of gesture function and mobile terminal | |
CN110928616A (en) | Shortcut icon management method and electronic equipment | |
CN110210197B (en) | Screen sensitivity adjusting method and mobile terminal |
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 |