Equipment interface jamming detection method and device, equipment and medium
By obtaining the current number of controls on the device interface, recording target change information, and comparing the number of controls thresholds, automated detection of device interface lag and abnormal control positioning are achieved, and the problem of not being able to determine the cause of lag in the existing technology is solved.
Patent Information
- Application Number
- CN202311176363.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-11
- Publication Date
- 2025-03-14
AI Technical Summary
The prior art is difficult to automatically detect the interface of the equipment stuttering, and it is impossible to determine the cause of the stuttering.
By obtaining the current number of controls in the device interface, determine the target change information corresponding to the current number of controls, and record it in the preset log file. The lag detection is performed based on the comparison results of the current control number and the preset control number threshold, and the exception control is located using the log file information to generate code.
It realizes automatic detection of device interface lags, and can quickly locate the abnormal controls that cause lags to generate code, so as to learn the cause of lags, which is easy to repair.
Smart Images
Figure CN119621523A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for detecting device interface freeze. Background Art
[0002] Currently, a heartbeat mechanism is usually used to detect whether a device interface is stuck. For example, a heartbeat signal is periodically sent to a target object. If the heartbeat response signal of the target object is not received within a preset time, it is considered that the interface corresponding to the currently running application to which the target object belongs is stuck. The advantage of this method is that the scope of detection is relatively wide. The disadvantage is that it will occupy a part of the network bandwidth resources due to the need to maintain signal transmission, and the heartbeat detection mechanism can only determine whether the current interface is stuck, but the cause of the stuck cannot be known.
[0003] In summary, how to automatically detect device interface freezes and find out the causes of freezes is a problem that needs to be solved. Summary of the invention
[0004] In view of this, the purpose of the present invention is to provide a device interface freeze detection method, device, equipment and medium, which can automatically detect device interface freeze and find out the cause of freeze. The specific scheme is as follows:
[0005] In a first aspect, the present application discloses a device interface freeze detection method, comprising:
[0006] Get the current number of controls in the device interface;
[0007] Determine the target change information corresponding to the current number of controls according to a preset information recording rule, and record the target change information in a preset log file;
[0008] The device interface is detected to be stuck based on the comparison result between the current number of controls and the preset control number threshold, and after the device interface is detected to be stuck, the abnormal control generation code is located using the information recorded in the preset log file.
[0009] Optionally, obtaining the current number of controls in the device interface includes:
[0010] Counting the number of current controls corresponding to each control type in the device interface to obtain the total number of current controls in the device interface;
[0011] The total number of current controls is determined as the current number of controls in the device interface.
[0012] Optionally, the determining target change information corresponding to the current number of controls includes:
[0013] If it is monitored that the increase in the current number of controls relative to the last counted number of historical controls is greater than the corresponding preset increase threshold, the change information corresponding to the current number of controls is used as the target change information.
[0014] Optionally, the determining target change information corresponding to the current number of controls includes:
[0015] If it is monitored that the current number of controls changes relative to the number of historical controls counted last time, the change information corresponding to the current number of controls is used as the target change information.
[0016] Optionally, the target change information corresponding to the current number of controls includes the corresponding control change number, control type and current business scenario.
[0017] Optionally, the locating the abnormal control generation code by using the information recorded in the preset log file includes:
[0018] Based on the control type and the current business scenario recorded in the preset log file, selecting a corresponding target control generation code from a preset control generation code library;
[0019] The abnormal control generation code is located from the target control generation code.
[0020] Optionally, locating the abnormal control generation code from the target control generation code includes:
[0021] Analyze the original normal program logic corresponding to the target control generation code to determine the corresponding number of normal business controls;
[0022] Determine a target control type corresponding to the target control generation code, and compare the control change quantity corresponding to the target control type recorded in the preset log file with the normal business control quantity;
[0023] If the control change quantity corresponding to the target control type is greater than the normal business control quantity, it is determined that the target control generation code is an abnormal control generation code that causes the current device interface to freeze.
[0024] Optionally, the device interface freeze detection method further includes:
[0025] The preset control quantity threshold value configured based on the experience information is obtained through the first input interface.
[0026] Optionally, the device interface freeze detection method further includes:
[0027] The largest target historical control quantity is selected from all historical control quantities corresponding to the historical non-stuck device interface as the preset control quantity threshold.
[0028] Optionally, the device interface freeze detection method further includes:
[0029] The target control quantity threshold corresponding to the scenario type of the current business scenario is searched from a pre-configured control quantity threshold library to obtain the preset control quantity threshold.
[0030] Optionally, the performing freeze detection on the device interface based on a comparison result between the current number of controls and a preset control number threshold includes:
[0031] If the current number of controls is greater than a preset control number threshold, it is determined that a freeze occurs on the current device interface;
[0032] If the current number of controls is not greater than the preset control number threshold, the current device interface is determined to be a non-stuck device interface, and an interface refresh operation is triggered to update the current device interface, and the process jumps back to the step of obtaining the current number of controls in the device interface.
[0033] Optionally, the device interface freeze detection method further includes:
[0034] After the device interface is detected to be stuck, the corresponding stuck alarm process is triggered, and a stuck alarm operation is performed on the device interface that is currently stuck based on a pop-up alarm and / or an assertion alarm.
[0035] In a second aspect, the present application discloses a device interface freeze detection device, comprising:
[0036] The control quantity acquisition module is used to obtain the current number of controls in the device interface;
[0037] A log recording module, used to determine target change information corresponding to the current number of controls, and record the target change information into a preset log file according to a preset information recording rule;
[0038] The abnormality locating module is used to detect the jamming of the device interface based on the comparison result between the current number of controls and the preset control number threshold, and after detecting the jamming of the device interface, use the information recorded in the preset log file to locate the abnormal control generation code.
[0039] In a third aspect, the present application discloses an electronic device, comprising:
[0040] Memory, used to store computer programs;
[0041] The processor is used to execute the computer program to implement the steps of the device interface freeze detection method disclosed above.
[0042] In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned device interface freeze detection method are implemented.
[0043] It can be seen that the present application obtains the current number of controls in the device interface; determines the target change information corresponding to the current number of controls, and records the target change information in the preset log file according to the preset information recording rules; performs a jam detection on the device interface based on the comparison result between the current number of controls and the preset number of controls threshold, and after detecting that the device interface is jammed, uses the information recorded in the preset log file to locate the abnormal control generation code. It can be seen that the present application counts and obtains the current number of controls in the device interface in real time, and also records the target change information corresponding to the current number of controls in the preset log file according to the preset information recording rules. The jam detection of the device interface can be realized by comparing the current number of controls with the preset number of controls threshold. If the device interface is jammed, the abnormal control generation code can be quickly located using the information recorded in the preset log file. That is, the present application only needs to obtain the current number of controls in the device interface to automatically detect the jam problem in the device interface, and can also use the information recorded in the preset log file to quickly locate the abnormal control generation code, so as to learn the cause of the jam, which is convenient for the corresponding technicians to repair the jam problem. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0045] Figure 1 This is a flow chart of a device interface freeze detection method disclosed in this application;
[0046] Figure 2 This is a flow chart of a specific device interface freeze detection method disclosed in this application;
[0047] Figure 3 This is a flow chart of another specific device interface freeze detection method disclosed in this application;
[0048] Figure 4A schematic diagram of a device interface freeze detection process disclosed in this application;
[0049] Figure 5 This is a schematic diagram of the structure of a device interface freeze detection device disclosed in this application;
[0050] Figure 6 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION
[0051] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.
[0052] Currently, a heartbeat mechanism is usually used to detect whether a device interface is stuck. The advantage of this method is that the scope of detection is relatively wide. The disadvantage is that it will occupy a part of the network bandwidth resources due to the need to maintain signal transmission. In addition, the heartbeat detection mechanism can only determine whether the current interface is stuck, but the cause of the stuck cannot be known. To this end, the embodiments of the present application disclose a device interface stuck detection method, device, equipment and medium, which can automatically detect the device interface stuck and learn the cause of the stuck.
[0053] See also Figure 1 As shown, the embodiment of the present application discloses a device interface freeze detection method, the method comprising:
[0054] Step S11: Obtain the current number of controls in the device interface.
[0055] In this embodiment, an automated script is used to perform machine operation to count and obtain the current number of controls in the device interface in real time. Specifically, the device interface may be an ultrasound device interface, and all controls in the ultrasound device interface may be managed as a control tree according to the inclusion relationship, and then the total number of controls on the control tree may be counted in real time to obtain the current number of controls in the ultrasound device interface. It should be noted that this application is not limited to ultrasound device interfaces, and various electronic device interfaces may be applicable.
[0056] In a specific implementation, the above-mentioned acquisition of the current number of controls in the device interface includes: counting the number of current controls corresponding to each control type in the device interface to obtain the total number of current controls in the device interface; and determining the total number of current controls as the current number of controls in the device interface. That is, the embodiment of the present application can specifically count the current number of controls of each type of control in the ultrasound device interface according to the control type classification, so as to obtain the total number of current controls in the ultrasound device interface, and determine the total number of current controls as the current number of controls in the ultrasound device interface. For example, assuming that there are three types of controls in the current ultrasound device interface, namely, button controls, table controls, and image controls; among them, the current number of controls corresponding to button controls is 5, the current number of controls corresponding to table controls is 200, and the current number of controls corresponding to image controls is 4, then the total number of current controls in the ultrasound device interface is 209.
[0057] Step S12: determining target change information corresponding to the current number of controls, and recording the target change information into a preset log file according to a preset information recording rule.
[0058] The preset information recording rule may be used to limit the way in which the target change information is recorded into the file.
[0059] Furthermore, the preset information recording rule can also be used to limit the content contained in the target change information. In this case, the target change information corresponding to the current number of controls is determined according to the preset information recording rule, and the target change information corresponding to the current number of controls is recorded in the preset log file according to the preset information recording rule.
[0060] In a specific implementation, when determining the target change information corresponding to the current number of controls according to the preset information recording rule, the target change information of the current total number of controls is specifically determined. The target change information here can specifically refer to the change in the total number of controls compared to the number of controls counted last time. For example, assuming that the current total number of controls is 209; accordingly, it is only necessary to determine the change in the current total number of controls 209 compared to the total number of controls counted last time, that is, in this embodiment, the target change information corresponds to the current total number of controls.
[0061] Step S13: Based on the comparison result between the current number of controls and the preset control number threshold, the device interface is detected to be stuck, and after the device interface is detected to be stuck, the abnormal control generation code is located using the information recorded in the preset log file.
[0062] In this embodiment, the jam detection of the ultrasound device interface can be achieved by comparing the current number of controls with the preset control number threshold. If the ultrasound device interface is detected to be jammed, the abnormal control generation code can be quickly located using the information recorded in the preset log file. That is, the present application only needs to obtain the current number of controls in the ultrasound device interface to automatically detect the jam problem in the ultrasound device interface. At the same time, the abnormal control generation code can be quickly located using the information recorded in the preset log file, thereby understanding the cause of the jam, and facilitating the corresponding technicians to repair the jam problem. By processing the generation of these unnecessary controls, the memory usage can be reduced, thereby solving the memory leak problem.
[0063] It can be seen that the present application obtains the current number of controls in the device interface; determines the target change information corresponding to the current number of controls, and records the target change information in the preset log file according to the preset information recording rules; performs a jam detection on the device interface based on the comparison result between the current number of controls and the preset number of controls threshold, and after detecting that the device interface is jammed, uses the information recorded in the preset log file to locate the abnormal control generation code. It can be seen that the present application counts and obtains the current number of controls in the device interface in real time, and also records the target change information corresponding to the current number of controls in the preset log file according to the preset information recording rules. The jam detection of the device interface can be realized by comparing the current number of controls with the preset number of controls threshold. If the device interface is jammed, the abnormal control generation code can be quickly located using the information recorded in the preset log file. That is, the present application only needs to obtain the current number of controls in the device interface to automatically detect the jam problem in the device interface, and can also use the information recorded in the preset log file to quickly locate the abnormal control generation code, so as to learn the cause of the jam, which is convenient for the corresponding technicians to repair the jam problem.
[0064] See also Figure 2 As shown, the embodiment of the present application discloses a specific device interface freeze detection method. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. Specifically, it includes:
[0065] Step S21: Obtain the current number of controls in the device interface.
[0066] Step S22: determining target change information corresponding to the current number of controls, and recording the target change information into a preset log file according to a preset information recording rule.
[0067] In a specific embodiment, the above-mentioned determination of the target change information corresponding to the current number of controls according to the preset information recording rule includes: if it is monitored that the number of controls increased by the current number of controls relative to the number of historical controls counted last time is greater than the corresponding preset increase number threshold, then the change information corresponding to the current number of controls is used as the target change information. That is, in this embodiment, it is determined whether the number of controls increased by the current number of controls relative to the number of historical controls counted last time is greater than the corresponding preset increase number threshold, that is, it is determined whether the current number of controls has increased abnormally. Only when the number of controls increased is greater than the preset increase number threshold, the change information corresponding to the current number of controls is used as the target change information and recorded in the preset log file. For example, assuming that the current number of controls is 200, the number of historical controls counted last time is 50, the number of controls increased is 150, and the preset increase number threshold is 100. At this time, the number of controls increased by 150 is greater than the preset increase number threshold 100, so the change information corresponding to the current number of controls is recorded in the preset log file; if the current number of controls is 100, no information is recorded.
[0068] It should be pointed out that the target change information corresponding to the current number of controls includes the corresponding number of control changes, control type and current business scenario. In a specific implementation, taking the ultrasound field as an example, all controls added compared to the last time are recorded, including the number of control changes (here mainly refers to the number of controls added), control type and current ultrasound business scenario; wherein, the current ultrasound business scenario refers to the specific operation of the user on the ultrasound device interface, and the current ultrasound business scenario can facilitate the subsequent positioning of the control generation code. Taking the increase in the number of controls mentioned in the above example as 150, it is determined which types of controls are in these 150 controls, how many controls are increased for each type of control, and the specific operation of the user on the ultrasound device interface. For example, among these 150 controls, there are 2 button controls, 2 table controls, and 146 image buttons. The operation currently performed by the user on the ultrasound device interface is to query patient information, and the above information is recorded in the preset log file.
[0069] In another specific embodiment, the above-mentioned determination of the target change information corresponding to the current number of controls according to the preset information recording rules includes: if it is monitored that the current number of controls has changed relative to the number of historical controls counted last time, then the change information corresponding to the current number of controls is used as the target change information. That is, in this embodiment, as long as it is monitored that the current number of controls has changed relative to the number of historical controls counted last time, the change information corresponding to the current number of controls is used as the target change information and is recorded in the preset log file. It should be pointed out that the number of changed controls is not limited here, nor is the size relationship between the current number of controls and the number of historical controls limited. In other words, as long as the current number of controls is inconsistent with the number of historical controls, the change information corresponding to the current number of controls is used as the target change information.
[0070] Specifically, the target change information corresponding to the current number of controls includes the corresponding number of control changes, the type of control, and the current ultrasound business scenario. That is, as long as the current number of controls changes relative to the number of historical controls counted last time, the current number of control changes (here refers to the number of controls increased or decreased), the type of control, and the current ultrasound business scenario are recorded in the preset log file.
[0071] Step S23: performing freeze detection on the device interface based on a comparison result between the current number of controls and a preset control number threshold.
[0072] Step S24: after detecting that the device interface freezes, based on the control type and the current business scenario recorded in the preset log file, select the corresponding target control generation code from the preset control generation code library.
[0073] In this embodiment, after the ultrasound device interface freezes, the control type recorded in the preset log file and the current ultrasound business scenario are used to filter the corresponding target control generation code from the preset control generation code library. That is, in this embodiment, the control type recorded in the preset log file and the current ultrasound business scenario can be matched to the specific target control generation code in the preset control generation code library.
[0074] Step S25: locating abnormal control generation code from the target control generation code.
[0075] In this embodiment, the abnormal control generation code is located from the filtered target control generation code. In a specific implementation, the above-mentioned locating the abnormal control generation code from the target control generation code includes: analyzing the original normal program logic corresponding to the target control generation code to determine the corresponding normal business control number; determining the target control type corresponding to the target control generation code, and comparing the control change number corresponding to the target control type recorded in the preset log file with the normal business control number; if the control change number corresponding to the target control type is greater than the normal business control number, then the target control generation code is determined to be the abnormal control generation code that causes the current device interface to freeze. It can be understood that the original normal program logic corresponding to the target control generation code is first analyzed to determine the corresponding normal business control number, that is, according to the original normal program logic, it is determined how many normal business controls need to be generated, and then the control change number corresponding to the target control type recorded in the preset log file is compared with the normal business control number. If the control change number corresponding to the target control type is greater than the normal business control number, then the target control generation code is determined to be the abnormal control generation code that causes the current ultrasound device interface to freeze. For example, according to the original normal program logic corresponding to the target control generation code, only three button-type controls need to be generated currently. However, the preset log file records that 3,000 button-type controls were generated. This means that an exception occurred during the execution of the target control generation code. Therefore, the target control generation code is the abnormal control generation code that causes the current ultrasound device interface to freeze.
[0076] Exemplarily, the original normal program logic can also be analyzed to determine the corresponding number of normal business control changes; the number of control changes corresponding to the target control type is compared with the number of normal business control changes. If the number of control changes corresponding to the target control type is greater than the number of normal business control changes, it is determined that the target control generation code is an abnormal control generation code that causes the current device interface to freeze.
[0077] It should be pointed out that the target control generation code corresponding to each control type needs to be analyzed one by one. For example, assuming that the current ultrasound device interface generates 3 table controls, 3,000 button controls, and 2 image controls, the table control generation code, button control generation code, and image control generation code corresponding to each control type are determined in turn according to these three control types and the current ultrasound business scenario. By analyzing the original normal program logic corresponding to the table control generation code and the image control generation code, it can be seen that the currently generated 3 table controls and 2 image controls meet the program logic requirements, and only the generated 3,000 button controls do not meet the program logic requirements. Therefore, the abnormal control generation code that causes the current ultrasound device interface to freeze is the button control generation code.
[0078] For more specific processing procedures of the above steps S21 and S23, reference may be made to the corresponding contents disclosed in the above embodiments, which will not be described in detail here.
[0079] It can be seen that in the embodiment of the present application, only when the number of controls increased by the current number of controls relative to the number of historical controls counted last time is greater than the preset increase number threshold, the change information corresponding to the current number of controls can be used as the target change information and recorded in the preset log file; or as long as it is monitored that the current number of controls has changed relative to the number of historical controls counted last time, the change information corresponding to the current number of controls can be used as the target change information and recorded in the preset log file. Among them, the change information corresponding to the current number of controls specifically includes the corresponding number of control changes, the control type and the current ultrasound business scenario. In addition, when locating the abnormal control generation code using the information recorded in the preset log file, firstly, based on the control type and the current ultrasound business scenario recorded in the preset log file, the corresponding target control generation code is screened from the preset control generation code library, and then the abnormal control generation code is located from the target control generation code.
[0080] See also Figure 3 and Figure 4 As shown, the embodiment of the present application discloses a specific device interface freeze detection method. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. Specifically, it includes:
[0081] Step S31: obtaining the current number of controls in a device interface, which may specifically be an interface of an ultrasound device.
[0082] Step S32: Determine the target change information corresponding to the current number of controls according to the preset information recording rule, and record the target change information in a preset log file. After the target change information is recorded in the preset log file, the process can jump to the step of refreshing the image to update the current ultrasound device interface.
[0083] Step S33: If the current number of controls is greater than a preset control number threshold, it is determined that a freeze occurs on the current device interface.
[0084] In this embodiment, it is only necessary to compare the current number of controls with the preset control number threshold. If the current number of controls is greater than the preset control number threshold, it is determined that the current ultrasound device interface is stuck, thereby realizing the detection of stuck on the ultrasound device interface.
[0085] In a specific implementation, the method further includes: obtaining, through the first input interface, the preset control quantity threshold value configured based on experience information. That is, the preset control quantity threshold value may be a value configured by the user based on experience information.
[0086] In another specific implementation, the method further includes: selecting the largest number of target historical controls from all the numbers of historical controls corresponding to the historical non-stuttering device interface as the preset control number threshold. That is, the largest number of target historical controls from all the numbers of historical controls corresponding to the historical non-stuttering ultrasound device interface can be set as the preset control number threshold.
[0087] In another specific implementation, the method further includes: searching for a target control quantity threshold corresponding to the scene type of the current business scene from a pre-configured control quantity threshold library to obtain the preset control quantity threshold. That is, control quantity thresholds under different scene types can be pre-configured and stored in a pre-configured control quantity threshold library, and then searching for a target control quantity threshold corresponding to the scene type of the current ultrasound business scene from the control quantity threshold library and setting it as the preset control quantity threshold.
[0088] Step S34: If the current number of controls is not greater than the preset control number threshold, the current device interface is determined to be a non-stuck device interface, and an interface refresh operation is triggered to update the current device interface, and the process jumps back to the step of obtaining the current number of controls in the device interface.
[0089] In this embodiment, Figure 4 As shown, if the current number of controls is not greater than the preset control number threshold, the current ultrasound device interface is determined to be a non-stuck ultrasound device interface, and the image refresh operation is triggered to update the current ultrasound device interface, and the process jumps again to the step of obtaining the current number of controls in the ultrasound device interface, and re-performs the stuttering detection.
[0090] Step S35: After detecting that the device interface is stuck, locate the abnormal control generation code using the information recorded in the preset log file.
[0091] Furthermore, the method further includes: after detecting that the device interface is stuck, triggering a corresponding stuck alarm process, and performing a stuck alarm operation on the device interface that is currently stuck based on a pop-up box alarm and / or an assertion alarm. It is understandable that after detecting that the ultrasound device interface is stuck, a corresponding stuck alarm process can also be triggered to perform a stuck alarm operation on the ultrasound device interface that is currently stuck, and the alarm method can include a pop-up box alarm and / or an assertion alarm.
[0092] For more specific processing procedures of the above steps S31, S32 and S35, reference may be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be described in detail here.
[0093] It can be seen that the embodiment of the present application needs to compare the current number of controls with the preset control number threshold. If the current number of controls is greater than the preset control number threshold, it is determined that the current device interface is stuck, thereby realizing the detection of stuck on the device interface. If the current number of controls is not greater than the preset control number threshold, the current device interface is determined to be a non-stuck device interface, and the interface refresh operation is triggered to update the current device interface, and jump back to the step of obtaining the current number of controls in the device interface, and re-perform the stuck detection. Furthermore, after detecting that the device interface is stuck, the corresponding stuck alarm process can also be triggered to perform a stuck alarm operation on the device interface that is currently stuck. The alarm method can include a pop-up box alarm and / or an assertion alarm.
[0094] See also Figure 5 As shown, the embodiment of the present application discloses a device interface freeze detection device, the device comprising:
[0095] The control quantity acquisition module 11 is used to obtain the current number of controls in the device interface;
[0096] The log recording module 12 is used to determine the target change information corresponding to the current number of controls, and record the target change information into a preset log file according to a preset information recording rule;
[0097] The abnormality locating module 13 is used to detect the freezing of the device interface based on the comparison result between the current number of controls and the preset control number threshold, and after detecting the freezing of the device interface, use the information recorded in the preset log file to locate the abnormal control generation code.
[0098] Since the embodiments of the device part correspond to the above embodiments, please refer to the description of the embodiments of the method part for the embodiments of the device part, and will not be repeated here.
[0099] It can be seen that the present application obtains the current number of controls in the device interface; determines the target change information corresponding to the current number of controls according to the preset information recording rules, and records the target change information in the preset log file according to the preset information recording rules; performs a jam detection on the device interface based on the comparison result between the current number of controls and the preset number of controls threshold, and after detecting that the device interface is jammed, uses the information recorded in the preset log file to locate the abnormal control generation code. It can be seen that the present application counts and obtains the current number of controls in the device interface in real time, and also records the target change information corresponding to the current number of controls in the preset log file according to the preset information recording rules. The jam detection of the device interface can be realized by comparing the current number of controls with the preset number of controls threshold. If the device interface is jammed, the abnormal control generation code can be quickly located using the information recorded in the preset log file. That is, the present application only needs to obtain the current number of controls in the device interface to automatically detect the jam problem in the device interface, and can also use the information recorded in the preset log file to quickly locate the abnormal control generation code, so as to learn the cause of the jam, which is convenient for the corresponding technicians to repair the jam problem.
[0100] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Specifically, it may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the device interface jam detection method performed by the electronic device disclosed in any of the aforementioned embodiments.
[0101] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.
[0102] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.
[0103] In addition, the memory 22, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon include an operating system 221, a computer program 222 and data 223, etc. The storage method can be temporary storage or permanent storage.
[0104] Among them, the operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, so as to realize the operation and processing of the massive data 223 in the memory 22 by the processor 21, which can be Windows, Unix, Linux, etc. In addition to including a computer program that can be used to complete the device interface jam detection method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks. In addition to data transmitted from an external device received by the electronic device, the data 223 can also include data collected by its own input and output interface 25, etc.
[0105] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the steps of the device interface freeze detection method disclosed in any of the aforementioned embodiments are implemented.
[0106] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.
[0107] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0108] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0109] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0110] The above is a detailed introduction to a device interface freeze detection method, apparatus, device and storage medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in the field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A device interface freeze detection method, characterized in that: include: Get the current number of controls in the device interface; Determine target change information corresponding to the current number of controls, and record the target change information into a preset log file according to a preset information recording rule; The device interface is detected to be stuck based on the comparison result between the current number of controls and the preset control number threshold, and after the device interface is detected to be stuck, the abnormal control generation code is located using the information recorded in the preset log file.
2. The device interface freeze detection method according to claim 1, characterized in that: The obtaining of the current number of controls in the device interface includes: Counting the number of current controls corresponding to each control type in the device interface to obtain the total number of current controls in the device interface; The total number of current controls is determined as the current number of controls in the device interface.
3. The device interface freeze detection method according to claim 2, characterized in that: The determining of target change information corresponding to the current number of controls includes: If it is monitored that the increase in the number of controls of the current number of controls relative to the number of historical controls counted last time is greater than the corresponding preset increase threshold, the change information corresponding to the current number of controls is used as the target change information; Or, if it is monitored that the current number of controls changes relative to the number of historical controls counted last time, the change information corresponding to the current number of controls is used as the target change information.
4. The device interface freeze detection method according to any one of claims 1 to 3, characterized in that: The target change information corresponding to the current number of controls includes the corresponding number of control changes, the type of control, and the current business scenario.
5. The device interface freeze detection method according to claim 4, characterized in that: The locating the abnormal control generation code by using the information recorded in the preset log file includes: Based on the control type and the current business scenario recorded in the preset log file, selecting a corresponding target control generation code from a preset control generation code library; The abnormal control generation code is located from the target control generation code.
6. The device interface freeze detection method according to claim 5, characterized in that: The locating the abnormal control generation code from the target control generation code includes: Analyze the original normal program logic corresponding to the target control generation code to determine the corresponding number of normal business controls; Determine a target control type corresponding to the target control generation code, and compare the control change quantity corresponding to the target control type recorded in the preset log file with the normal business control quantity; If the control change quantity corresponding to the target control type is greater than the normal business control quantity, it is determined that the target control generation code is an abnormal control generation code that causes the current device interface to freeze.
7. The device interface freeze detection method according to any one of claims 1 to 3, characterized in that: Also includes: Acquire the preset control quantity threshold value configured based on experience information through the first input interface; Or, the largest target historical control quantity is selected from all historical control quantities corresponding to the historical non-stuttering device interface as the preset control quantity threshold; Or, a target control quantity threshold corresponding to the scenario type of the current business scenario is searched from a pre-configured control quantity threshold library to obtain the preset control quantity threshold.
8. The device interface freeze detection method according to any one of claims 1 to 3, characterized in that: The performing freeze detection on the device interface based on the comparison result between the current number of controls and a preset control number threshold includes: If the current number of controls is greater than a preset control number threshold, it is determined that a freeze occurs on the current device interface; If the current number of controls is not greater than the preset control number threshold, the current device interface is determined to be a non-stuck device interface, and an interface refresh operation is triggered to update the current device interface, and the process jumps back to the step of obtaining the current number of controls in the device interface.
9. The device interface freeze detection method according to any one of claims 1 to 3, characterized in that: Also includes: After the device interface is detected to be stuck, the corresponding stuck alarm process is triggered, and a stuck alarm operation is performed on the device interface that is currently stuck based on a pop-up alarm and / or an assertion alarm.
10. A device interface freeze detection device, characterized in that: include: The control quantity acquisition module is used to obtain the current number of controls in the device interface; A log recording module, used to determine target change information corresponding to the current number of controls, and record the target change information into a preset log file according to a preset information recording rule; The abnormality locating module is used to detect the jamming of the device interface based on the comparison result between the current number of controls and the preset control number threshold, and after detecting the jamming of the device interface, use the information recorded in the preset log file to locate the abnormal control generation code.
11. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor is used to execute the computer program to implement the steps of the device interface freeze detection method as described in any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the steps of the device interface freeze detection method as described in any one of claims 1 to 9 are implemented.