CN111352791A - System application detection method and device, terminal equipment and storage medium - Google Patents
System application detection method and device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN111352791A CN111352791A CN201811561030.4A CN201811561030A CN111352791A CN 111352791 A CN111352791 A CN 111352791A CN 201811561030 A CN201811561030 A CN 201811561030A CN 111352791 A CN111352791 A CN 111352791A
- Authority
- CN
- China
- Prior art keywords
- time
- component
- starting
- target
- application process
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
- G06F11/3419—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Abstract
The invention is suitable for the technical field of operating system management, and provides a method and a device for detecting system application and terminal equipment, wherein the method comprises the following steps: acquiring starting time from the creation of a target application process to the completion of the loading of a target component; comparing the starting time with the expected time calibrated by the target component to obtain the time difference of starting the target application process; and if the time difference is larger than a preset time difference value, judging that the target application process is blocked. The invention can realize the refined detection of the starting process condition of the system application, is convenient for the system to be optimized in time and ensures the smoothness of the system application process during operation.
Description
Technical Field
The invention belongs to the technical field of operating system management, and particularly relates to a method and a device for detecting system application, terminal equipment and a storage medium.
Background
With the development of internet technology, an operating system of a mobile terminal can support more and more application processes; in the system operation process, response time and system fluency are important indexes of an operating system. When the operating system starts a plurality of application processes, the processes are easy to block or fail due to limited hardware resources of the system, so that the operating system is easy to be blocked or failed.
At present, the running condition of the system application can be adjusted only through a frequency modulation mechanism of an operating system, or the abnormal condition can be detected only when the application process reaches a certain time, and the detection of the system application process still has certain defects.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for detecting a system application, a terminal device, and a storage medium, so as to solve the problem that a certain defect still exists in detecting a system application process.
A first aspect of an embodiment of the present invention provides a method for detecting a system application, including:
acquiring starting time from the creation of a target application process to the completion of the loading of a target component;
comparing the starting time with the expected time calibrated by the target component to obtain the time difference of starting the target application process;
and if the time difference is larger than a preset time difference value, judging that the target application process is blocked.
In one embodiment, before obtaining the start time of the target application process from the creation process to the completion of the loading of the target component, the method comprises the following steps:
judging whether the current component is a component preloaded for the first time in the creating process;
if the current assembly is an assembly preloaded for the first time in the creating process, judging whether the current assembly has the calibrated expected time;
and if the current assembly has the calibrated expected time, determining that the current assembly is the target assembly.
In one embodiment, obtaining the start time of the target application process from the creation process to the completion of the loading of the target component comprises:
recording a first time for starting a creating process and a second time for completing the loading of the target component;
and determining the starting time of the target application process according to the first time and the second time.
In one embodiment, comparing the starting time with an expected time calibrated by a target component, and obtaining a time difference of starting of the target application process comprises:
and calculating the starting timeout rate of the target application process according to the starting time and the expected time, wherein the timeout rate is the ratio of the starting time to the expected time.
In one embodiment, if the time difference is greater than a preset time difference, determining that the target application process is stuck includes:
and generating timeout information according to the timeout rate, and feeding the timeout information back to a system process management unit.
A second aspect of an embodiment of the present invention provides a detection apparatus for system application, including:
the first computing module is used for acquiring the starting time from the creation process to the completion of the loading of the target component of the target application process;
the second calculation module is used for comparing the starting time with the expected time calibrated by the target component to obtain the time difference of starting the target application process;
and the judging module is used for judging that the target application process is stuck if the time difference is greater than a preset time difference value.
In one embodiment, the detection device applied by the system further comprises:
the first judgment module is used for judging whether the current component is a component which is preloaded for the first time in the creation process;
a second judging module, configured to judge whether the current component has the calibrated expected time if the current component is a component to be preloaded for the first time in the creation process;
and the component determination module is used for determining that the current component is the target component if the current component has the calibrated expected time.
In one embodiment, the first calculation module comprises:
the first recording unit is used for recording a first time for starting the creation process and a second time for finishing the loading of the target component;
and the second recording unit is used for determining the starting time of the target application process according to the first time and the second time.
In one embodiment, the determination module comprises:
and the information generating unit is used for generating timeout information according to the timeout rate and feeding the timeout information back to the system process management unit.
A third aspect of the embodiments of the present invention provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the detection method applied by the system when executing the computer program.
A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the detection method applied by the system described above.
Compared with the prior art, the embodiment of the invention has the following beneficial effects: according to the embodiment of the invention, the starting time of the target application process from the creation process to the loading completion of the target component is obtained, the starting time is compared with the expected time of the target component, the starting time difference of the target application process is obtained, and if the time difference is greater than the preset time difference value, the target application process is judged to be stuck, so that the starting condition of the system application process is finely detected, the application process is timely optimized, the smoothness of the system application process during operation is ensured, and the method and the device have strong usability and practicability.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flow chart illustrating an implementation of a detection method for a system application according to an embodiment of the present invention;
fig. 2 is a schematic overall implementation flow diagram of a system application detection method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of a detection apparatus applied to a system according to a third embodiment of the present invention;
fig. 4 is a schematic diagram of a terminal device according to a fourth embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
The terms "comprises" and "comprising," and any variations thereof, in the description and claims of this application and the drawings described above, are intended to cover non-exclusive inclusions. For example, a process, method, or system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. Furthermore, the terms "first," "second," and "third," etc. are used to distinguish between different objects and not to describe a particular order
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
Example one
Referring to fig. 1, which is a schematic flow chart illustrating an implementation process of the detection method for system applications provided in the embodiment of the present invention, the method may be used for detecting performance fluency of a terminal device, and an operating system of the terminal device may support multiple application processes to run, for example, a mobile phone with an android system, a tablet computer, a robot, and the like. The method may comprise the steps of:
step S101, acquiring the starting time from the creation process to the completion of the loading of the target component of the target application process.
In the embodiment of the invention, when the application in the system is started, a corresponding application program needs to be loaded; each application program can correspond to one or more components, the components are basic building blocks of the application program, and each component is a service entrance of the system entering the application program; each component independently exists and jointly completes the function of the application program; for example, four broad classes of components are included for the android system. When an application program starts a certain component, a process is a carrier for carrying the component, the process corresponding to the component is started first, and if the process corresponding to the component does not exist, the process corresponding to the component needs to be created.
The target application process can be an application program with high use frequency or more important in the system; the target component can be an important or main component defined in a certain application program, and can also be a configured component; the start time for the target application process to complete the launch includes the creation time of the process and the load time of the component.
It should be noted that the start time of the target application process must be the complete time of the first loading of the component after the process creation is completed, including the creation time of the process corresponding to the first loaded component. After the process is created, if the same component is loaded for the second time, the process does not need to be created, the process can be directly loaded and called, and the time for completing the loading of the component for the second time is not recorded if the component loaded for the second time does not meet the requirement of the target component.
In one embodiment, before obtaining the start time of the target application process from the creation process to the completion of the loading of the target component, the method comprises the following steps:
a1, judging whether the current component is the component preloaded for the first time in the creating process.
In this embodiment, each process may correspond to multiple components, such as an active component or a service component. Each process can support multiple loads of the same type of component, and after the process is created, the corresponding process does not need to be created any more by reloading the same component. When the application program loads the components, the corresponding process is started first, and then the corresponding components are loaded; when detecting whether an application process is blocked or not, the method detects a component which is started for the first time after the process creation process is completed, so that after the process creation is completed, the preloaded component process needs to be judged, whether the current component is the component which is preloaded for the first time or not is judged, the time for initially creating the process and the time for completing the loading of the component are accurately recorded, and the completeness and the reasonability of the starting time of the application process are ensured.
In addition, the first-loaded component may be a main component of a system application or a most commonly-used component, such as a chat application supported by the system, and an active component corresponding to the open chat interface may be designated as the main component of the application; after the application program is started and the corresponding activity component is called, other service components are called, for example, a payment function in the chat application, the chat interface is returned again, the activity component is called again, the calling is not the first time, and the activity component called for the second time does not meet the requirement of the target component.
A2, if the current component is the component preloaded for the first time in the creating process, judging whether the current component has the calibrated expected time.
In this embodiment, if it is determined that the current component is a component to be first loaded by the created process, it is determined whether there is a calibration expected time in the current component in the calling process, where the expected time is a time for starting an expected completion of an application process, and includes a time for creating the process and a time for first loading the component; the expected time may configure corresponding time information in an application configuration table. The application program configuration table is used for configuring corresponding attributes for the process of the system when the multi-process application program runs, forming a configuration table, and starting the configured components according to the configuration table. The process of loading the component may determine whether the current component loaded has passed the expected time calibration.
In addition, if the current component is not the component loaded for the first time in the process, judging whether the starting time of the current component is already calculated; if the starting time of the current assembly is calculated, ending the detection process of whether the application process is stuck; if the starting time of the current component is not calculated, the starting time of the current component is signed, for example, marked as-1, so that the loaded component can be distinguished and judged when the application process is started.
A3, if the current component has the expected time, determining that the current component is the target component.
In this embodiment, when the system applies and loads the component, if the process corresponding to the component does not exist, the corresponding process is created first, and the time point of creating the corresponding process is recorded; after the process is established, the loaded current assembly is judged, whether the current assembly is the assembly started for the first time after the process is established or not is judged, and whether the current assembly is calibrated with the assembly with expected time or not is judged. And if the current component is a component started for the first time after the process creation is completed and the current component is calibrated, judging that the current component is a target component.
In this embodiment, only by comparing the actual time of the loaded component of the application program with the expected time calibrated by the component, whether the application program is jammed in the running process can be accurately judged; the current assembly has the expected calibration time, and has the basis for comparing with the actual starting time, and the current assembly meeting the requirements meets the condition of the system application pause detection.
In one embodiment, obtaining the start time of the target application process from the creation process to the completion of the loading of the target component comprises:
b1, recording a first time for starting a creation process and a second time for completing the loading of the target component;
b2, determining the starting time of the target application process according to the first time and the second time.
In this embodiment, the first time is the time when the process starts to be created, and may be recorded as T0The second time is the time when the current process completes loading the target component with calibration for the first time, and may be recorded as T1Calculating the starting time required by the target application process to complete the starting according to the first time and the second time, where the starting time may be recorded as △ T, and the calculation formula is as follows:
ΔT＝T1-T0(1)。
in one embodiment, the detection method applied by the system further comprises:
if the current assembly is the assembly which is preloaded for the first time of the process, and the current assembly does not calibrate the expected time, the time for completing the loading of the current assembly is calculated, and the time for completing the loading of the current assembly is used as a reference basis for calibrating the expected time of the current assembly.
In this embodiment, if the current component is a component loaded for the first time in the process but the expected time of the component is not calibrated, the time when the current component is loaded is obtained, the starting time of the current component is recorded, and the calibration of the expected loading time of the current component is referred to.
And S102, comparing the starting time with the expected time calibrated by the target component, and acquiring the time difference of starting the target application process.
In this embodiment, the starting time is an actual starting time from the process start of the target application process to the completion of the target component loading, the expected time is an expected loading time calibrated by the target component, the two are compared, and the time difference of the starting process of the target application process is calculated.
In one embodiment, comparing the starting time with an expected time calibrated by a target component, and obtaining a time difference of starting of the target application process comprises:
and calculating the starting timeout rate of the target application process according to the starting time and the expected time, wherein the timeout rate is the ratio of the starting time to the expected time.
In this embodiment, the starting time is the actual starting time of the target application process and may be recorded as △ T, the expected time is the expected loading time calibrated at the target component and may be recorded as Tb(ii) a And when the starting time is greater than the expected time, the actual starting time of the target application process is delayed compared with the expected loading time, and then the corresponding timeout rate is calculated according to the starting time and the expected time.
The timeout rate is the ratio of the starting time to the expected time, and the timeout rate can be expressed as D1Then, the calculation formula is:
in addition, if the starting time is equal to the expected time, the timeout rate is not calculated any more, and if the starting time of the system application is within the expected time range, it is determined that the system application process is not stuck.
And step S103, if the time difference is larger than a preset time difference value, determining that the target application process is stuck.
In this embodiment, the preset time difference may be set according to a specific application scenario of an application program in the system; and if the time difference is not within the preset time difference range, judging that the target application process has a pause phenomenon.
In one embodiment, if the time difference is greater than a preset time difference, determining that the target application process is stuck includes:
and generating timeout information according to the timeout rate, and feeding the timeout information back to a system process management unit.
In this embodiment, the preset timeout rate preset may be DdIndicating that if the timeout rate is greater than the predetermined timeout rate threshold, D1>DbAnd if so, jamming occurs in the running process of the current application, generating timeout information according to the timeout rate of the process loaded by the current application, feeding the timeout information back to the system adjusting unit, and performing optimization operation on the system application.
It should be noted that, in the process of running the system application, the creation time of the process, the record of the loading time of the component, and the calculation of the timeout rate can all be managed and controlled by the activity management service activitymanager service process; the method for detecting the loading completion time of the four major components of the android system is consistent, and the method is not only suitable for the time from the process starting to the Activity loading completion of the Activity, but also suitable for the loading situations of other components, so that the detection of the system running condition can be accurate to each application program, the system application is detected, the karton phenomenon is found in time, and the adjustment and optimization are carried out in time; and the smoothness of the important application process of the system during operation is ensured.
It should be noted that, within the technical scope of the present disclosure, other sequencing schemes that can be easily conceived by those skilled in the art should also be within the protection scope of the present disclosure, and detailed description is omitted here.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Example two
Fig. 2 is a schematic diagram of an overall implementation flow of the system application detection method according to the first embodiment of the present invention, which is the same as the first embodiment of the present invention in principle, and classifies multiple situations according to the judgment part of the current component.
Step S201, acquiring a first moment when the application process starts to create the process, and loading a current component after the process creation is completed;
step S202, judging whether the current assembly is the assembly loaded for the first time in the process; if yes, executing step S203, otherwise executing step S204;
step S203, if the current component is the component loaded for the first time in the process, judging whether the current component has the calibrated expected time; if yes, executing step S206, otherwise executing step S207;
step S204, if the current assembly is not the assembly loaded for the first time in the process, judging whether the starting time of the current assembly is calculated; if yes, go to step S210, otherwise go to step S205;
step S205, if the starting time of the current assembly is not calculated, the starting time of the current assembly is signed, and step S210 is executed;
step S206, obtaining a second moment when the current assembly finishes loading, determining the actual starting time of the application process according to the first moment and the second moment, comparing the actual starting time with the expected time, and calculating the timeout rate if the actual starting time is greater than the expected time; step 208 is executed;
step S207, if the expected time is not calibrated, calculating the starting time of the current component according to the time of loading the component and the time of process creation, and executing step S210;
step S208, judging whether the timeout rate is greater than a preset timeout rate threshold value; if yes, executing step S209, otherwise executing step S210;
step S209, if the timeout rate is greater than the preset timeout rate threshold, generating timeout information, feeding back the timeout information to the process management unit of the system, and executing step S210;
step S210, ending the detection process of whether the current running process is stuck.
The embodiment and the detection method described in the first embodiment are basically the same in principle implementation, and the steps are not described in detail here.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
EXAMPLE III
Fig. 3 is a schematic diagram of a detection apparatus applied to the system according to the embodiment of the present invention, and for convenience of description, only the relevant parts to the embodiment of the present invention are shown.
The detection device includes:
the first calculation module 31 is configured to obtain a start time from creation of the target application process to completion of loading of the target component;
the second calculation module 32 is configured to compare the start time with an expected time calibrated by a target component, and obtain a time difference for starting the target application process;
and the determining module 33 is configured to determine that the target application process is stuck if the time difference is greater than a preset time difference.
In one embodiment, the detection device further comprises:
the first judgment module is used for judging whether the current component is a component which is preloaded for the first time in the creation process;
a second judging module, configured to judge whether the current component has the calibrated expected time if the current component is a component to be preloaded for the first time in the creation process;
and the component determination module is used for determining that the current component is the target component if the current component has the calibrated expected time.
In one embodiment, the first calculation module comprises:
the first recording unit is used for recording a first time for starting the creation process and a second time for finishing the loading of the target component;
and the second recording unit is used for determining the starting time of the target application process according to the first time and the second time.
In one embodiment, the determination module comprises:
and the information generating unit is used for generating timeout information according to the timeout rate and feeding the timeout information back to the system process management unit.
The starting time of the target assembly of the current application after starting is obtained through the embodiment, the starting time is compared with the expected time for calibrating the target assembly, whether the preset condition is met or not is judged, the starting process condition of the system application is finely detected, the system is convenient to optimize in time, and the smoothness of the system application process during operation is guaranteed.
It will be apparent to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely illustrated, and in practical applications, the above function distribution may be performed by different functional units and modules as needed, that is, the internal structure of the mobile terminal is divided into different functional units or modules to perform all or part of the above described functions. Each functional module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional modules are only used for distinguishing one functional module from another, and are not used for limiting the protection scope of the application. The specific working process of the module in the mobile terminal may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.
Example four
Fig. 4 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 4, the terminal device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42, such as a program for calculating time, stored in said memory 41 and executable on said processor 40. The processor 40, when executing the computer program 42, implements the steps in the detection method embodiments of the various system applications described above, such as the steps S101 to S103 shown in fig. 1. Alternatively, the processor 40, when executing the computer program 42, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the modules 31 to 33 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to implement the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 42 in the terminal device 4. For example, the computer program 42 may be divided into a first computing module, a first computing module and a determining module, and each module has the following specific functions:
the first computing module is used for acquiring the starting time from the creation process to the completion of the loading of the target component of the target application process;
the second calculation module is used for comparing the starting time with the expected time calibrated by the target component and acquiring the starting timeout rate of the target application process;
and the judging module is used for judging that the target application process is stuck if the overtime rate is greater than a preset overtime threshold.
The terminal device 4 may be a computing device such as a robot, a mobile phone, a palm computer, and a cloud server. The terminal device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of a terminal device 4 and does not constitute a limitation of terminal device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input-output devices, network access devices, buses, etc.
The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or a memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used for storing the computer program and other programs and data required by the terminal device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components 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 units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media which may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A method for detecting a system application, comprising:
acquiring starting time from the creation of a target application process to the completion of the loading of a target component;
comparing the starting time with the expected time calibrated by the target component to obtain the time difference of starting the target application process;
and if the time difference is larger than a preset time difference value, judging that the target application process is blocked.
2. The method for detecting system applications according to claim 1, before obtaining the start time of the target application process from the creation process to the completion of the loading of the target component, comprising:
judging whether the current component is a component preloaded for the first time in the creating process;
if the current assembly is an assembly preloaded for the first time in the creating process, judging whether the current assembly has the calibrated expected time;
and if the current assembly has the calibrated expected time, determining that the current assembly is the target assembly.
3. The method for detecting system applications according to claim 1, wherein obtaining the start time of the target application process from the creation process to the completion of the loading of the target component comprises:
recording a first time for starting a creating process and a second time for completing the loading of the target component;
and determining the starting time of the target application process according to the first time and the second time.
4. The method for detecting system applications according to claim 1, wherein comparing the starting time with an expected time for target component calibration to obtain the time difference for starting the target application process comprises:
and calculating the starting timeout rate of the target application process according to the starting time and the expected time, wherein the timeout rate is the ratio of the starting time to the expected time.
5. The method for detecting system applications according to claim 4, wherein if the time difference is greater than a preset time difference, determining that the target application process is stuck comprises:
and generating timeout information according to the timeout rate, and feeding the timeout information back to a system process management unit.
6. A system application detection apparatus, comprising:
the first computing module is used for acquiring the starting time from the creation process to the completion of the loading of the target component of the target application process;
the second calculation module is used for comparing the starting time with the expected time calibrated by the target component to obtain the time difference of starting the target application process;
and the judging module is used for judging that the target application process is blocked if the time difference is greater than a preset time value.
7. The system-applied detection apparatus of claim 6, further comprising:
the first judgment module is used for judging whether the current component is a component which is preloaded for the first time in the creation process;
a second judging module, configured to judge whether the current component has the calibrated expected time if the current component is a component to be preloaded for the first time in the creation process;
and the component determination module is used for determining that the current component is the target component if the current component has the calibrated expected time.
8. The system application detection apparatus of claim 6, wherein the first calculation module comprises:
the first recording unit is used for recording a first time for starting the creation process and a second time for finishing the loading of the target component;
and the second recording unit is used for determining the starting time of the target application process according to the first time and the second time.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 5 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811561030.4A CN111352791A (en) | 2018-12-20 | 2018-12-20 | System application detection method and device, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811561030.4A CN111352791A (en) | 2018-12-20 | 2018-12-20 | System application detection method and device, terminal equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111352791A true CN111352791A (en) | 2020-06-30 |
Family
ID=71195292
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811561030.4A Pending CN111352791A (en) | 2018-12-20 | 2018-12-20 | System application detection method and device, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111352791A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113568748A (en) * | 2021-07-27 | 2021-10-29 | Oppo广东移动通信有限公司 | Application process processing method and device, storage medium and electronic equipment |
| CN114168222A (en) * | 2021-11-29 | 2022-03-11 | 北京博睿宏远数据科技股份有限公司 | Method and device for acquiring starting time, terminal equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6324546B1 (en) * | 1998-10-12 | 2001-11-27 | Microsoft Corporation | Automatic logging of application program launches |
| CN104199692A (en) * | 2014-08-25 | 2014-12-10 | 北京金山安全软件有限公司 | Method, device and terminal for acquiring starting time of application program |
| CN105573755A (en) * | 2015-12-15 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for acquiring application Activity rendering time |
| CN108984395A (en) * | 2018-06-21 | 2018-12-11 | 腾讯科技（北京）有限公司 | A kind of application program launching time-consuming test method, device and storage medium |
-
2018
- 2018-12-20 CN CN201811561030.4A patent/CN111352791A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6324546B1 (en) * | 1998-10-12 | 2001-11-27 | Microsoft Corporation | Automatic logging of application program launches |
| CN104199692A (en) * | 2014-08-25 | 2014-12-10 | 北京金山安全软件有限公司 | Method, device and terminal for acquiring starting time of application program |
| CN105573755A (en) * | 2015-12-15 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for acquiring application Activity rendering time |
| CN108984395A (en) * | 2018-06-21 | 2018-12-11 | 腾讯科技（北京）有限公司 | A kind of application program launching time-consuming test method, device and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113568748A (en) * | 2021-07-27 | 2021-10-29 | Oppo广东移动通信有限公司 | Application process processing method and device, storage medium and electronic equipment |
| CN114168222A (en) * | 2021-11-29 | 2022-03-11 | 北京博睿宏远数据科技股份有限公司 | Method and device for acquiring starting time, terminal equipment and storage medium |
| CN114168222B (en) * | 2021-11-29 | 2023-10-17 | 北京博睿宏远数据科技股份有限公司 | Method and device for acquiring time consumption during starting, terminal equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP2017531865A (en) | Event-based computer vision calculation | |
| CN110021792B (en) | Charging control method and device, terminal equipment and computer storage medium | |
| US20210176174A1 (en) | Load balancing device and method for an edge computing network | |
| CN110908865A (en) | Memory leakage monitoring method and device and electronic equipment | |
| WO2016023520A1 (en) | Method and device for recognizing application causing temperature rise of terminal, and terminal | |
| CN112996020B (en) | Bluetooth-based automatic test method and device and Bluetooth test terminal | |
| CN113535721A (en) | Data writing method and device | |
| CN104267980A (en) | Software score display method, terminal, data server and system | |
| CN111897660B (en) | Model deployment method, model deployment device and terminal equipment | |
| CN111352791A (en) | System application detection method and device, terminal equipment and storage medium | |
| CN104363112A (en) | Parameter management method and parameter management device | |
| CN112333246B (en) | ABtest experiment method and device, intelligent terminal and storage medium | |
| CN108733478B (en) | Three-dimensional image processing method and device | |
| CN114168318A (en) | Training method of storage release model, storage release method and equipment | |
| CN107526955B (en) | Screen-off unlocking method and device | |
| CN111597009A (en) | Application program display method and device and terminal equipment | |
| CN113272785B (en) | Method for mounting file system, terminal equipment and storage medium | |
| CN111159009A (en) | Pressure testing method and device for log service system | |
| CN105204903A (en) | Process module loading interception method and device | |
| CN115587545A (en) | Parameter optimization method, device and equipment for photoresist and storage medium | |
| CN105487849A (en) | Method and system for calling unknown export functions of DLL | |
| CN112747946B (en) | Equipment structure damage detection method and device | |
| CN111222739B (en) | Nuclear power station task allocation method and nuclear power station task allocation system | |
| CN109388564B (en) | Test method and device and electronic equipment | |
| US10872019B2 (en) | Load and save recovery partition using mobile device |
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 |