CN112685088A - Method, device and equipment for protecting application operation and readable storage medium - Google Patents
Method, device and equipment for protecting application operation and readable storage medium Download PDFInfo
- Publication number
- CN112685088A CN112685088A CN201910988821.3A CN201910988821A CN112685088A CN 112685088 A CN112685088 A CN 112685088A CN 201910988821 A CN201910988821 A CN 201910988821A CN 112685088 A CN112685088 A CN 112685088A
- Authority
- CN
- China
- Prior art keywords
- application
- killing
- module
- component
- value
- 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.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a method, a device, equipment and a readable storage medium for protecting application operation, wherein the method comprises the following steps: responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing; when the process comprises a killing prevention component, setting a maximum memory exhaustion adjusting value of the process as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold value for killing the process; the application is started. That is, in the embodiment of the present invention, by inserting an anti-killing component into a process corresponding to an application to be protected in advance, in an application starting process, if the process corresponding to the started application includes the anti-killing component, a maximum memory exhaustion adjustment value of the process is set to be a preset adjustment value, and since the preset adjustment value is smaller than a minimum killing threshold value for killing the process, the process is not killed by an application management measure, so that the started application can be effectively protected from running continuously.
Description
Technical Field
The embodiment of the invention relates to the technical field of mobile terminals, in particular to a method, a device, equipment and a readable storage medium for protecting application operation.
Background
With the development of wireless communication technology, various functions and various applications that a mobile terminal can bear are increasing, and the types and the number of the applications are increasing, so that the adverse effects on the response speed, the fluency, the power consumption, the memory and the like of an operating system are also increasing.
In order to ensure the normal operation of the mobile terminal, a series of application management measures are proposed at present, for example, when the system resources are scarce, the system may kill some background applications, so as to release more system resources. At present, a common method is to set a memory occupation threshold for all applications, then monitor the running applications, and directly kill all background applications occupying memory larger than the set threshold.
However, the above-mentioned method may result in that some applications that the user does not want to be killed are killed hard, and the normal use of the user is interrupted, i.e. the false killing situation is easy to occur.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a readable storage medium for protecting application operation, which aim to overcome the technical problem that the application is easy to kill by mistake in the conventional application management measures.
In a first aspect, an embodiment of the present invention provides a method for protecting an application from running, where the method includes:
responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing;
when the progress comprises an anti-killing component, setting a maximum memory exhaustion adjusting value of the progress as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold for killing the progress;
and starting the application.
In one possible design, further comprising:
adding the identifier of the application to a white list of the sleep Doze mode, wherein the application in the white list is not frozen in the Doze mode.
In one possible design, after the starting the application, the method further includes:
acquiring an application cleaning list of a currently running power saving program;
and determining whether the application exists in the application cleaning list, and if so, removing the application from the application cleaning list.
In a possible design, before the setting the maximum memory exhaustion adjustment value of the process as the preset adjustment value, the method further includes:
reading a system configuration file, and determining a minimum killing threshold for killing the process;
determining the preset adjustment value based on the minimum kill threshold.
In one possible design, before determining whether a process corresponding to the application includes an anti-killing component in response to an application start instruction, the method includes:
reading a system configuration file, and determining an application needing protection;
and inserting the anti-killing component into a process corresponding to the application needing protection.
In a second aspect, an embodiment of the present invention provides an apparatus for protecting an application from running, where the apparatus includes:
the response module is used for responding to an application starting instruction and determining whether a process corresponding to the application comprises a component for preventing killing;
the anti-killing module is used for setting a maximum memory exhaustion adjusting value of the progress to be a preset adjusting value when the progress comprises an anti-killing component, and the preset adjusting value is smaller than a minimum killing threshold value for killing the progress;
and the starting module is used for starting the application.
In one possible design, further comprising:
an anti-freeze module to add the identification of the application to a white list of the Doze mode, the application in the white list not being frozen in the Doze mode.
In one possible design, further comprising:
the acquisition module is used for acquiring an application cleaning list of a currently running power-saving program after the application is started;
a removing module, configured to determine whether the application exists in the application clear list, and if the application exists in the application clear list, remove the application from the application clear list.
In one possible design, the anti-killing module includes:
the first reading module is used for reading a system configuration file and determining a minimum killing threshold for killing the process;
a determining module, configured to determine the preset adjustment value based on the minimum killing threshold.
In one possible design, further comprising:
the second reading module is used for reading the system configuration file and determining the application needing to be protected;
and the inserting module is used for inserting the anti-killing component into a process corresponding to the application needing protection.
In a third aspect, an embodiment of the present invention provides an apparatus, including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of protecting application execution as provided in the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method for protecting the application from running is implemented as provided in the first aspect.
The method, the device, the equipment and the readable storage medium for protecting the application operation provided by the embodiment of the invention can realize that: responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing; when the process comprises a killing prevention component, setting a maximum memory exhaustion adjusting value of the process as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold value for killing the process; the application is started. That is, in the embodiment of the present invention, by inserting an anti-killing component into a process corresponding to an application to be protected in advance, in an application starting process, if the process corresponding to the started application includes the anti-killing component, a maximum memory exhaustion adjustment value of the process is set to be a preset adjustment value, and since the preset adjustment value is smaller than a minimum killing threshold value for killing the process, the process is not killed by an application management measure, so that the started application can be effectively protected from running continuously.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a first flowchart illustrating a method for protecting an application from running according to an embodiment of the present invention;
fig. 2 is a second flowchart illustrating a method for protecting application operation according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating an operation principle of a power saving program in a method for protecting an application from running according to an embodiment of the present invention;
fig. 4 is a first schematic block diagram of an apparatus for protecting an application from running according to an embodiment of the present invention;
fig. 5 is a second schematic block diagram of an apparatus for protecting application operation according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a hardware structure of an apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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, but 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.
The embodiment of the invention provides a method for protecting application operation, which can be applied to electronic equipment such as a mobile terminal and the like, such as a mobile phone, a tablet computer, a notebook computer, an intelligent watch, a vehicle-mounted terminal and the like.
Referring to fig. 1, fig. 1 is a first flowchart illustrating a method for protecting application operation according to an embodiment of the present invention, where in the embodiment of the present invention, the method includes:
s101, responding to an application starting instruction, and determining whether a process corresponding to the application comprises a component for preventing killing.
The Application includes Application software (App for short) running on the mobile terminal.
In this embodiment, the applications that need to be protected in the mobile terminal, such as some monitoring applications that need to be run online at proper time, may be predetermined according to the usage requirements of the user, and if the applications are killed by the management program inside the mobile terminal during the running process, unnecessary loss may be brought to the user.
For an application which needs to be protected, a component for preventing killing, such as activity, service and the like, can be inserted into a corresponding process in advance.
In addition, in a possible embodiment, the system configuration file may also be read in advance, the application needing to be protected is determined, and then the anti-killing component is inserted into the process corresponding to the application needing to be protected.
For example, a cust configuration file of the mobile terminal may be obtained in advance, and an application that needs to be protected may be read from the cust configuration file.
Specifically, when monitoring a start instruction triggered by a user, the mobile terminal responds to the start instruction and judges whether a process corresponding to the application contains a component for preventing killing in the process of starting the related application.
S102, when the progress comprises the anti-killing component, setting the maximum memory exhaustion adjusting value of the progress as a preset adjusting value, wherein the preset adjusting value is smaller than the minimum killing threshold for killing the progress.
The cleaning mechanism in the Android system includes an Out-Of-Memory Killer (short for OOM Killer) mechanism and a Low Memory Killer mechanism.
In the OOM Killer mechanism, when the system cannot reallocate the memory, the kernel traverses all processes, calculates the value of badness for each process, and kills the process with the largest badness. One of the factors affecting the process badness value is the memory exhaustion adjustment value (oom _ score _ adj).
In the Low Memory Killer mechanism, 6 Memory levels that can be set and corresponding oom _ score _ adj values are provided, and processes with oom _ score _ adj values greater than a certain specified value are all killed when the system Memory is below each level.
That is, both the OOM Killer and LowMemoryKiller mechanisms in the Android system use OOM _ score _ adj values to determine whether to clean the process. The oom _ score _ adj value is used to mark the importance of each process, and the value range is generally-1000 to 1000, the smaller the oom _ score _ adj value is, the more important the process is, otherwise, the less important the process is.
In addition, there is a maximum memory exhaustion adjustment value (maxAdj value) in the Android system that is used in the system to define the maximum value of oom _ score _ adj for some system critical processes.
In the embodiment of the present invention, in order to prevent the process of the application that needs to be protected from being cleaned up by the system, the maxAdj value of the process is set to be kept at a smaller value, so as to ensure that the OOM _ score _ adj value of the process is kept in a Low state all the time, thereby effectively preventing the process from being killed by the OOM Killer and Low Memory Killer mechanisms.
In the embodiment of the present invention, the system configuration file may be read in advance, the minimum killing threshold for killing the process may be determined, and then the preset adjustment value may be determined based on the minimum killing threshold.
Specifically, the preset adjustment value is smaller than a minimum kill threshold for killing the process.
In a possible embodiment of the present invention, the preset adjustment value may be 1. I.e., the maxAdj value of the above process may be set to 1.
And S103, starting the application.
In the embodiment of the present invention, after the maximum memory exhaustion adjustment value of the process is set as the preset adjustment value, the application to be protected may be started.
After the application is started, the maxAdj value of the process corresponding to the application is smaller than the minimum killing threshold for killing the process, so that the process cannot be killed by the system application management program, and can continuously run.
The method for protecting the application operation provided by the embodiment of the invention comprises the following steps: responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing; when the process comprises a killing prevention component, setting a maximum memory exhaustion adjusting value of the process as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold value for killing the process; the application is started. That is, in the embodiment of the present invention, by inserting an anti-killing component into a process corresponding to an application to be protected in advance, in an application starting process, if the process corresponding to the started application includes the anti-killing component, a maximum memory exhaustion adjustment value of the process is set to be a preset adjustment value, and since the preset adjustment value is smaller than a minimum killing threshold value for killing the process, the process is not killed by an application management measure, so that the started application can be effectively protected from running continuously.
Further, based on the content described in the foregoing embodiment, referring to fig. 2, fig. 2 is a schematic flow chart of a method for protecting application operation according to an embodiment of the present invention, where in the embodiment of the present invention, the method includes:
s201, responding to an application starting instruction, and determining whether a process corresponding to the application comprises a component for preventing killing.
S202, when the progress comprises the anti-killing component, setting the maximum memory exhaustion adjusting value of the progress as a preset adjusting value, wherein the preset adjusting value is smaller than the minimum killing threshold for killing the progress.
S203, starting the application.
S204, adding the application identifier into a white list of the Doze mode, wherein the applications in the white list cannot be frozen in the Doze mode.
The contents described in the steps S201 to S203 are the same as the contents described in the steps S101 to S103 in the above embodiment, and the description in the above embodiment may be specifically referred to, and are not repeated herein.
In most mobile terminals, besides the killing process mechanism, there is also a process freezing mechanism, i.e. Doze, in the mobile phone system. When the mobile terminal is not connected with a power line and is left for a long time, the mobile terminal enters a Doze mode, and in the Doze mode, although an application process still exists, the application process is in a sleep state, and partial functions such as network access are suspended, so that the application cannot receive a message sent by a server in real time.
In the embodiment of the present invention, after it is ensured that the application process is not killed, in order to further ensure normal and continuous operation of the application, a situation that the process is frozen needs to be prevented.
In particular, the identity of the application that needs to be protected may be added to the white list of the Doze mode, and the application in the white list may not be frozen in the Doze mode. After the mobile terminal enters the Doze mode, the applications in the white list can be omitted, so that the applications needing to be protected are not frozen.
In addition, in another possible embodiment, the application needing to be protected may be read in the system cust configuration file when the mobile terminal is powered on, and then the application needing to be protected may be added to the white list of Doze.
The method for protecting the application operation provided by the embodiment of the invention can prevent the application needing to be protected from being killed and also can prevent the application needing to be protected from being frozen, so that the application needing to be protected can be effectively protected from continuously operating.
Further, based on the content described in the foregoing embodiment, in the embodiment of the present invention, after the application that needs to be protected is started, the method further includes:
acquiring an application cleaning list of a currently running power saving program; and determining whether the application needing to be protected exists in the application clear list, and if the application needing to be protected exists in the application clear list, removing the application needing to be protected from the application clear list.
It can be understood that, at present, in order to prolong the standby time of the mobile terminal, some power saving programs are pre-installed in the mobile terminal, and the power saving programs clean application processes running on the mobile terminal according to a certain rule, so as to reduce the power consumption of the mobile terminal.
In the embodiment of the invention, the application cleaning list of the currently running power saving program can be acquired, and the application needing to be protected is removed from the application cleaning list, so that the application needing to be protected can be prevented from being cleaned by the power saving program.
Referring to fig. 3, fig. 3 is a schematic diagram illustrating an operation principle of a power saving program in a method for protecting application operation according to an embodiment of the present invention, where in the embodiment of the present invention, the power saving program generally completes an action of killing a process by calling an application Clean With Callback (request App Clean With Callback) method in a Multi Task Manager Service (Multi Task Manager Service) after some internal logic judgment is performed. That is, the power saving program sends an application Clean request to a multitask Manager (Multi Task Manager), and after receiving the application Clean request, the multitask Manager sends an application Clean message (request App Clean With Callback) to the multitask Manager service to complete the action of killing the process.
In this embodiment, modification may be performed in the multitask manager service, filtering logic is added in the method of cleaning the process, and cleaning is not performed for the application that needs to be killed. Therefore, the purpose that the application needing protection is not cleaned by the power-saving program is achieved.
It is understood that the above method for preventing the power saving program from being cleared may be used alone, or may be used in combination with the method for protecting the application from running described in fig. 1, or may be used in combination with the method for protecting the application from running described in fig. 2.
That is, the method for protecting application operation provided in the embodiment of the present invention may not only prevent an application to be protected from being killed by an OOM Killer and LowMemoryKiller mechanism, but also prevent the application to be protected from being cleaned up by a power saving program, and/or prevent the application to be protected from being frozen, so that the application to be protected can be effectively protected from continuously operating.
Further, based on the method for protecting application operation described in the foregoing embodiment, an embodiment of the present invention further provides an apparatus for protecting application operation, referring to fig. 4, where fig. 4 is a first schematic block diagram of the apparatus for protecting application operation provided in the embodiment of the present invention, and in the embodiment of the present invention, the apparatus 40 for protecting application operation includes:
the response module 401 is configured to determine, in response to the application start instruction, whether a process corresponding to the application includes a component for preventing killing.
An anti-killing module 402, configured to set a maximum memory exhaustion adjustment value of the process to a preset adjustment value when the process includes an anti-killing component, where the preset adjustment value is smaller than a minimum killing threshold for killing the process.
A starting module 402, configured to start the application.
In a feasible implementation manner, referring to fig. 5, fig. 5 is a second schematic block diagram of an apparatus for protecting application operation according to an embodiment of the present invention, in which the apparatus 40 for protecting application operation further includes:
an anti-freeze module 501, configured to add the identifier of the application to a white list of the Doze mode, where the application in the white list is not frozen in the Doze mode.
In a possible embodiment, the device 40 for protecting the application running further includes:
and the acquisition module is used for acquiring an application cleaning list of the currently running power saving program after the application is started. A removing module, configured to determine whether the application exists in the application clear list, and if the application exists in the application clear list, remove the application from the application clear list.
In one possible embodiment, the anti-killing module 402 includes:
the first reading module is used for reading the system configuration file and determining the minimum killing threshold for killing the process. And the determining module is used for determining the preset adjusting value based on the minimum killing threshold value.
In a possible embodiment, the device 40 for protecting the application running further includes:
and the second reading module is used for reading the system configuration file and determining the application needing protection. And the inserting module is used for inserting the anti-killing component into a process corresponding to the application needing protection.
The functions and principles that can be implemented by the device 40 for protecting application operation are the same as those described in the method for protecting application operation provided in the above embodiment, and specific contents may refer to the description in the embodiment corresponding to the method for protecting application operation, and are not described herein again.
The device for protecting the application operation provided by the embodiment of the invention can realize that: responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing; when the process comprises a killing prevention component, setting a maximum memory exhaustion adjusting value of the process as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold value for killing the process; the application is started. That is, in the embodiment of the present invention, by inserting an anti-killing component into a process corresponding to an application to be protected in advance, in an application starting process, if the process corresponding to the started application includes the anti-killing component, a maximum memory exhaustion adjustment value of the process is set to be a preset adjustment value, and since the preset adjustment value is smaller than a minimum killing threshold value for killing the process, the process is not killed by an application management measure, so that the started application can be effectively protected from running continuously.
Further, based on the method for protecting the application operation described in the foregoing embodiment, an embodiment of the present invention further provides an apparatus, where the apparatus includes: at least one processor and memory; the memory stores computer-executable instructions; the at least one processor executes computer-executable instructions stored in the memory to cause the at least one processor to perform the method of protecting application operation as described in the above embodiments.
For better understanding of the embodiment of the present invention, referring to fig. 6, fig. 6 is a schematic diagram of a hardware structure of an apparatus according to the embodiment of the present invention. As shown in fig. 6, the apparatus 60 of the present embodiment includes: a processor 601 and a memory 602; wherein
A memory 602 for storing computer-executable instructions.
The processor 601 is configured to execute the computer execution instructions stored in the memory to implement the steps performed by the mobile terminal in the above embodiments. Reference may be made in particular to the description relating to the method embodiments described above.
Alternatively, the memory 602 may be separate or integrated with the processor 601.
When the memory 602 is provided separately, the device further comprises a bus 603 for connecting said memory 602 and the processor 601.
The device provided in this embodiment may be used to implement the technical solution of the method embodiment, and the implementation principle and technical effect are similar, which are not described herein again.
Further, the embodiment of the present invention also provides a computer-readable storage medium, in which computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method for protecting the application running is implemented as described above.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules is only one logical division, and other divisions may be realized in practice, for example, a plurality of modules may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each module may exist alone physically, or two or more modules are integrated into one unit. The unit formed by the modules can be realized in a hardware form, and can also be realized in a form of hardware and a software functional unit.
The integrated module implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present application.
It should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.
The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile storage NVM, such as at least one disk memory, and may also be a usb disk, a removable hard disk, a read-only memory, a magnetic or optical disk, etc.
The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The storage medium may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the storage medium may reside as discrete components in an electronic device or host device.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (12)
1. A method for protecting application execution, the method comprising:
responding to an application starting instruction, and determining whether a process corresponding to the application contains a component for preventing killing;
when the progress comprises an anti-killing component, setting a maximum memory exhaustion adjusting value of the progress as a preset adjusting value, wherein the preset adjusting value is smaller than a minimum killing threshold for killing the progress;
and starting the application.
2. The method of claim 1, further comprising:
adding the identifier of the application to a white list of the sleep Doze mode, wherein the application in the white list is not frozen in the Doze mode.
3. The method according to claim 1 or 2, wherein after the starting the application, further comprising:
acquiring an application cleaning list of a currently running power saving program;
and determining whether the application exists in the application cleaning list, and if so, removing the application from the application cleaning list.
4. The method of claim 3, wherein before setting the maximum memory drain adjustment value of the process to the preset adjustment value, further comprising:
reading a system configuration file, and determining a minimum killing threshold for killing the process;
determining the preset adjustment value based on the minimum kill threshold.
5. The method of claim 3, wherein before determining whether the application-corresponding process includes the anti-killing component in response to the application-start instruction, the method comprises:
reading a system configuration file, and determining an application needing protection;
and inserting the anti-killing component into a process corresponding to the application needing protection.
6. An apparatus for protecting an application from running, the apparatus comprising:
the response module is used for responding to an application starting instruction and determining whether a process corresponding to the application comprises a component for preventing killing;
the anti-killing module is used for setting a maximum memory exhaustion adjusting value of the progress to be a preset adjusting value when the progress comprises an anti-killing component, and the preset adjusting value is smaller than a minimum killing threshold value for killing the progress;
and the starting module is used for starting the application.
7. The apparatus of claim 6, further comprising:
an anti-freeze module to add the identification of the application to a white list of the Doze mode, the application in the white list not being frozen in the Doze mode.
8. The apparatus of claim 6 or 7, further comprising:
the acquisition module is used for acquiring an application cleaning list of a currently running power-saving program after the application is started;
a removing module, configured to determine whether the application exists in the application clear list, and if the application exists in the application clear list, remove the application from the application clear list.
9. The apparatus of claim 8, wherein the anti-killing module comprises:
the first reading module is used for reading a system configuration file and determining a minimum killing threshold for killing the process;
a determining module, configured to determine the preset adjustment value based on the minimum killing threshold.
10. The apparatus of claim 8, further comprising:
the second reading module is used for reading the system configuration file and determining the application needing to be protected;
and the inserting module is used for inserting the anti-killing component into a process corresponding to the application needing protection.
11. An apparatus, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of protecting application execution of any of claims 1 to 5.
12. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement a method of protecting application execution as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910988821.3A CN112685088A (en) | 2019-10-17 | 2019-10-17 | Method, device and equipment for protecting application operation and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910988821.3A CN112685088A (en) | 2019-10-17 | 2019-10-17 | Method, device and equipment for protecting application operation and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112685088A true CN112685088A (en) | 2021-04-20 |
Family
ID=75444848
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910988821.3A Pending CN112685088A (en) | 2019-10-17 | 2019-10-17 | Method, device and equipment for protecting application operation and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112685088A (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103324536A (en) * | 2012-03-23 | 2013-09-25 | 宇龙计算机通信科技(深圳)有限公司 | Terminal and application program protection method |
| CN103677978A (en) * | 2013-12-30 | 2014-03-26 | Tcl集团股份有限公司 | Method and electronic device for protecting processes |
| CN105653934A (en) * | 2015-12-25 | 2016-06-08 | 惠州Tcl移动通信有限公司 | Mobile terminal and application protection method thereof |
| CN105718791A (en) * | 2014-12-01 | 2016-06-29 | Tcl集团股份有限公司 | Method and apparatus for protecting application program data |
| CN106445604A (en) * | 2016-09-29 | 2017-02-22 | 深圳市邦华电子有限公司 | Clearing method and device for applications |
| CN107168792A (en) * | 2017-04-24 | 2017-09-15 | 宇龙计算机通信科技(深圳)有限公司 | A kind of process management method and terminal device |
| CN107249074A (en) * | 2017-05-16 | 2017-10-13 | 努比亚技术有限公司 | Application program quick start method, mobile terminal and computer-readable recording medium |
| CN107589994A (en) * | 2017-08-16 | 2018-01-16 | 深圳市爱培科技术股份有限公司 | Method, equipment, system and the storage medium of application process priority management |
| CN108055693A (en) * | 2017-10-26 | 2018-05-18 | 努比亚技术有限公司 | A kind of terminal applies control method, terminal and computer readable storage medium |
| CN108804207A (en) * | 2017-04-28 | 2018-11-13 | 珠海全志科技股份有限公司 | A kind of process management-control method based on android system |
| CN110096347A (en) * | 2019-03-29 | 2019-08-06 | 努比亚技术有限公司 | A kind of process back-stage management method, terminal and computer readable storage medium |
| CN110221921A (en) * | 2019-06-13 | 2019-09-10 | 深圳Tcl新技术有限公司 | EMS memory management process, terminal and computer readable storage medium |
-
2019
- 2019-10-17 CN CN201910988821.3A patent/CN112685088A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103324536A (en) * | 2012-03-23 | 2013-09-25 | 宇龙计算机通信科技(深圳)有限公司 | Terminal and application program protection method |
| CN103677978A (en) * | 2013-12-30 | 2014-03-26 | Tcl集团股份有限公司 | Method and electronic device for protecting processes |
| CN105718791A (en) * | 2014-12-01 | 2016-06-29 | Tcl集团股份有限公司 | Method and apparatus for protecting application program data |
| CN105653934A (en) * | 2015-12-25 | 2016-06-08 | 惠州Tcl移动通信有限公司 | Mobile terminal and application protection method thereof |
| CN106445604A (en) * | 2016-09-29 | 2017-02-22 | 深圳市邦华电子有限公司 | Clearing method and device for applications |
| CN107168792A (en) * | 2017-04-24 | 2017-09-15 | 宇龙计算机通信科技(深圳)有限公司 | A kind of process management method and terminal device |
| CN108804207A (en) * | 2017-04-28 | 2018-11-13 | 珠海全志科技股份有限公司 | A kind of process management-control method based on android system |
| CN107249074A (en) * | 2017-05-16 | 2017-10-13 | 努比亚技术有限公司 | Application program quick start method, mobile terminal and computer-readable recording medium |
| CN107589994A (en) * | 2017-08-16 | 2018-01-16 | 深圳市爱培科技术股份有限公司 | Method, equipment, system and the storage medium of application process priority management |
| CN108055693A (en) * | 2017-10-26 | 2018-05-18 | 努比亚技术有限公司 | A kind of terminal applies control method, terminal and computer readable storage medium |
| CN110096347A (en) * | 2019-03-29 | 2019-08-06 | 努比亚技术有限公司 | A kind of process back-stage management method, terminal and computer readable storage medium |
| CN110221921A (en) * | 2019-06-13 | 2019-09-10 | 深圳Tcl新技术有限公司 | EMS memory management process, terminal and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107957906A (en) | Application management method, computer installation, the computer-readable recording medium of terminal device | |
| CN110806925B (en) | Audio playing method and equipment | |
| CN108205474B (en) | Memory management method, terminal device, computer apparatus, and readable storage medium | |
| CN111277836B (en) | Video extraction frame loss control method, system, terminal and storage medium | |
| CN110895524B (en) | Composite overdue method, device, server and storage medium of full-load redis time key | |
| CN108205498B (en) | Memory recovery method and device, computer device and computer readable storage medium | |
| CN114257551A (en) | Distributed current limiting method and system and storage medium | |
| CN114546634B (en) | Management of synchronous restart of system | |
| CN111984413A (en) | Memory recovery method and device, electronic equipment and storage medium | |
| CN109521970B (en) | Data processing method and related equipment | |
| CN103677893A (en) | Method for reducing size of image file of starting up and arithmetic device | |
| CN112685088A (en) | Method, device and equipment for protecting application operation and readable storage medium | |
| CN113412480B (en) | Mounting processing method, mounting processing device, electronic equipment and computer readable storage medium | |
| CN107589907B (en) | Data processing method, electronic device and computer readable storage medium | |
| CN110633148A (en) | System operation optimization method and device, electronic equipment and storage medium | |
| CN115587049A (en) | Memory recovery method and device, electronic equipment and storage medium | |
| CN112230753B (en) | ARM server power key shutdown method, system, terminal and storage medium | |
| CN114090465A (en) | Memory recovery method and device | |
| CN115168052A (en) | Self-adaptive memory recovery control method, device, terminal and storage medium | |
| CN107643951B (en) | Process processing method and device and electronic equipment | |
| CN112148548B (en) | Method, device and equipment for determining starting times | |
| CN107357672B (en) | Data processing method and device | |
| CN114143574B (en) | Method for cleaning storage space, storage medium and terminal equipment | |
| CN111078714B (en) | Data processing method and device | |
| CN117493222A (en) | Memory recycling method and device and electronic equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210420 |