CN113127239A - Page state monitoring method, device, terminal and storage medium - Google Patents
Page state monitoring method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN113127239A CN113127239A CN201911410635.8A CN201911410635A CN113127239A CN 113127239 A CN113127239 A CN 113127239A CN 201911410635 A CN201911410635 A CN 201911410635A CN 113127239 A CN113127239 A CN 113127239A
- Authority
- CN
- China
- Prior art keywords
- page
- target page
- target
- display
- heartbeat log
- 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
- 238000012544 monitoring process Methods 0.000 title claims abstract description 76
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000002159 abnormal effect Effects 0.000 claims abstract description 67
- 238000011084 recovery Methods 0.000 claims abstract description 28
- 238000004590 computer program Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 description 8
- 238000004458 analytical method Methods 0.000 description 7
- 230000007547 defect Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 244000035744 Hura crepitans Species 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application is suitable for the technical field of computers, and provides a page state monitoring method, which comprises the following steps: monitoring a heartbeat log output by a preset thread for controlling the display of a target page, and determining the display state of the target page according to the monitoring result of the heartbeat log; and executing display state recovery operation on the target page when the display state of the target page is determined to be the display abnormal state. The abnormal page display method and the abnormal page display device can quickly and accurately determine the abnormal page display and timely and effectively recover the abnormal page display.
Description
Technical Field
The present application belongs to the field of computer technologies, and in particular, to a method, an apparatus, a terminal, and a storage medium for monitoring a page status.
Background
At present, when the browser page loads too much content or the browser page needs to perform high-intensity calculation, the situation that the page is rushed easily occurs. However, since the browser page itself is operated in the sandbox mode, the page repair cannot be performed effectively in time when a rushing situation occurs.
Disclosure of Invention
In view of this, embodiments of the present application provide a page status monitoring method, an apparatus, a terminal, and a storage medium, so as to solve the problem in the prior art that page repair cannot be performed timely and effectively.
A first aspect of an embodiment of the present application provides a remote page status monitoring method, including:
receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page;
monitoring a heartbeat log, wherein the heartbeat log is output by a preset thread for controlling the display of the target page;
determining a display state of the target page based on the heartbeat log;
and if the display state of the target page is the display abnormal state, executing display state recovery operation on the target page.
In an optional implementation manner, after receiving a page loading instruction carrying page attribute information, loading and displaying a target page based on the page attribute information includes:
after receiving a page loading instruction carrying page attribute information, starting a corresponding browser;
and loading and displaying the target page in the browser based on the page attribute information.
In an optional implementation manner, the display state of the target page includes a display abnormal state and a display normal state;
the determining the display state of the target page based on the heartbeat log includes:
if the heartbeat log is not captured in the current monitoring period, determining that the target page is in an abnormal display state;
and if the heartbeat log is captured in the current monitoring period, determining that the target page is in a normal display state.
In an optional implementation manner, if the display state of the target page is a display abnormal state, the performing, on the target page, a display state recovery operation includes:
if the display state of the target page is a display abnormal state, controlling a preset daemon thread to load first target data;
and restoring the display state of the target page according to the first target data.
In an alternative implementation, the first target data is used to refresh the target page;
the restoring the display state of the target page according to the first target data includes:
and refreshing the target page according to the first target data.
In an optional implementation manner, after the refreshing the target page according to the first target data, the method further includes:
monitoring the heartbeat log within a first preset time period;
if the heartbeat log is captured within the first preset time period, determining that the target page is restored to display a normal state;
if the heartbeat log is not captured within the first preset time period, controlling the preset daemon thread to load the second target data, wherein the second target data is used for reloading the target page;
and reloading the target page according to the second target data.
In an optional implementation manner, after the reloading the target page according to the second target data, the method further includes:
monitoring the heartbeat log within a second preset time period;
if the heartbeat log is captured within the second preset time period, determining that the target page is restored to display a normal state;
and if the heartbeat log is not captured in the second preset time period, sending prompt information of displaying abnormal states of the target page to a predetermined terminal.
A second aspect of the embodiments of the present application provides a page status monitoring apparatus, including:
the loading module is used for receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page;
the monitoring module is used for monitoring a heartbeat log, and the heartbeat log is output by a preset thread for controlling the display of the target page;
the determining module is used for determining the display state of the target page based on the heartbeat log;
and the recovery module is used for executing display state recovery operation on the target page if the display state of the target page is the display abnormal state.
In an optional implementation manner, the loading module includes:
the starting unit is used for starting a corresponding browser after detecting a page loading instruction which is triggered by a user and carries page attribute information;
and the first loading unit is used for loading and displaying the target page in the browser based on the page attribute information.
In an optional implementation manner, the display state of the target page includes a display abnormal state and a display normal state;
the determining module includes:
the first determining unit is used for determining that the target page is in an abnormal display state if the heartbeat log is not captured in the current monitoring period;
and the second determining unit is used for determining that the target page is in a normal display state if the heartbeat log is captured in the current monitoring period.
In an optional implementation manner, the recovery module includes:
the first control unit is used for controlling a preset daemon thread to load first target data if the display state of the target page is a display abnormal state;
and the restoring unit is used for restoring the display state of the target page according to the first target data.
In an alternative implementation, the first target data is used to refresh the target page;
the recovery unit is specifically configured to:
and refreshing the target page according to the first target data.
In an optional implementation manner, the recovery module further includes:
the first monitoring unit is used for monitoring the heartbeat log in a first preset time period;
a third determining unit, configured to determine that the target page resumes to display a normal state if the heartbeat log is captured within the first preset time period;
the second control unit is configured to control the preset daemon thread to load the second target data if the heartbeat log is not captured within the first preset time period, where the second target data is used to reload the target page;
and the second loading unit is used for reloading the target page according to the second target data.
In an optional implementation manner, the recovery module further includes:
the second monitoring unit is used for monitoring the heartbeat log in a second preset time period;
a fourth determining unit, configured to determine that the target page resumes to display a normal state if the heartbeat log is captured within the second preset time period;
and the sending unit is used for sending prompt information of displaying abnormal states of the target page to a predetermined terminal if the heartbeat log is not captured in the second preset time period.
A third aspect of the embodiments of the present application provides a terminal, including 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 page status monitoring method according to the first aspect when executing the computer program.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where a computer program is stored, where the computer program, when executed by a processor, implements the steps of the page status monitoring method according to the first aspect.
Compared with the prior art, the page state monitoring method provided by the embodiment of the application has the advantages that the display state of the target page is determined by monitoring the heartbeat logs output by the preset threads for controlling the display of the target page and according to the monitoring result of the heartbeat logs; and when the display state of the target page is determined to be the display abnormal state, the display state recovery operation is executed on the target page, the display abnormal page can be rapidly and accurately determined, and timely and effective recovery is realized for the display abnormal page.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, 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 application, 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 flowchart illustrating an implementation of a page status monitoring method according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating an implementation of S101 shown in FIG. 1;
FIG. 3 is a flowchart illustrating an implementation of S103 in FIG. 1;
FIG. 4 is a flowchart of a specific implementation of S104 in the first embodiment in FIG. 1;
FIG. 5 is a flowchart of a second embodiment of the implementation of S104 in FIG. 1;
FIG. 6 is a flowchart of a third embodiment of the implementation of S104 in FIG. 1;
fig. 7 is a schematic structural diagram of a page status monitoring apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
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 present application. It will be apparent, however, to one skilled in the art that the present application 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 application with unnecessary detail.
It should be noted that when the browser page loads too much content or performs high-density computation, due to a vulnerability of the program itself for controlling the browser page and a stability problem of the browser itself, the browser page runs for a period of time. The browser page is operated in a sandbox mode, once the page rushing condition occurs, the problem cannot be timely and effectively found, page recovery is carried out aiming at the problem, and therefore the page needs to be stably operated for a long time, such as an outdoor advertising screen.
In view of this, the present application provides a page status monitoring scheme, which can timely and effectively recover a page with abnormal display, and solve the problem that a browser page cannot stably run for a long time.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples. Fig. 1 is a flowchart illustrating an implementation of a page status monitoring method according to an embodiment of the present application. The present embodiment may be implemented by hardware or software of a page status monitoring apparatus, where the page status monitoring apparatus is a terminal device with a computing function, such as an outdoor display device. The details are as follows:
s101, receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page.
It is understood that the page loading instruction may be triggered by the user through a physical button or a virtual button of the current terminal device, or may be sent directly by the user and other terminal devices. The page attribute information is attribute information which is configured in advance and comprises basic display information such as width and height of a page, an access address of the page and the like.
And after the current terminal equipment receives the page loading instruction, loading a corresponding target page based on the access address of the page, and displaying according to the basic display information of the page.
In an alternative implementation manner, as shown in fig. 2, it is a flowchart of a specific implementation of S101 in fig. 1. As can be seen from fig. 2, S101 includes S1011 to S1012. The details are as follows:
and S1011, after receiving the page loading instruction carrying the page attribute information, starting the corresponding browser.
It should be noted that, in an alternative implementation, a fixed browser is pre-installed on the terminal device, where the browser may generally support systems such as Microsoft Windows 7, Server 2008, macOS, Linux, SmartOS, IBM AIX, and FreeBSD, such as google browser, and a js interface suite, such as puppeteer, for operating the browser is deployed on the terminal device.
After receiving a page loading instruction carrying page attribute information, starting a browser through a corresponding js interface set, for example, starting a google browser through puppeteer.
S1012, loading and displaying the target page in the browser based on the page attribute information.
It can be understood that, after the browser is started, the browser enters a target page to be rendered and displayed according to the page attribute information, so that the target page is loaded in the browser and displayed.
As can be seen from the above analysis, in this embodiment, the corresponding browser is started, the target page is loaded and displayed in the browser, and the target page can be controlled according to the characteristics of the browser, so that the target page is conveniently operated.
S102, monitoring a heartbeat log, wherein the heartbeat log is output by a preset thread for controlling the target page to display.
It should be noted that, while the target page is loaded in the browser, a preset thread is configured for the target page, where the preset thread is used to control display of the target page and output a heartbeat log based on a preset heartbeat log output logic, for example, the preset heartbeat log output logic includes configuring a heartbeat log packet for the preset thread in advance, and if the preset thread is controlled in the process of displaying the target page and an abnormal display state is not monitored, a heartbeat log is periodically output based on the heartbeat log packet or a heartbeat log is continuously output based on the heartbeat log packet; and if the abnormal display state is monitored in the process of controlling the target page display by the preset thread, the heartbeat log cannot be output by the preset thread. S103, determining the display state of the target page based on the heartbeat log.
It can be known from the analysis of S102 that, when the target page displays a normal state, the preset thread outputs a heartbeat log based on preset heartbeat log output logic, and when the target page displays an abnormal state, the preset thread does not output a heartbeat log, so that the terminal device can determine the display state of the target page based on the heartbeat log.
It should be noted that the display states of the target page include a display abnormal state and a display normal state; in an alternative implementation, as shown in fig. 3, it is a flowchart of a specific implementation of S103 in fig. 1. As can be seen from fig. 3, S103 includes S1031 to S1032. The details are as follows:
and S1031, if the heartbeat log is not captured in the current monitoring period, determining that the target page is in an abnormal display state.
According to the preset heartbeat log output logic, in the process that the preset thread controls the target page to display, if the abnormal display is monitored, the preset thread is controlled not to output the heartbeat log. Therefore, if the heartbeat log is not captured in the current monitoring period, it is determined that the target page is in an abnormal display state.
S1032, if the heartbeat log is captured in the current monitoring period, it is determined that the target page is in a normal display state.
In the same way, according to the preset heartbeat log output logic, in the process that the preset thread controls the target page to display, if the target page is monitored to be normally displayed, the preset thread is controlled to periodically output the heartbeat log or continuously output the heartbeat log. Therefore, if the heartbeat log is captured in the current monitoring period, it is determined that the target page is in a normal display state.
Through the analysis, the display state of the target page can be determined according to whether the heartbeat log is captured in the current monitoring period, whether the target page is abnormal can be rapidly and accurately monitored, and timely early warning and repairing are achieved.
And S104, if the display state of the target page is the display abnormal state, executing display state recovery operation on the target page.
In an optional implementation manner, a daemon thread is set for the target page in advance, and when it is determined that the display state of the target page is the display abnormal state, the display state recovery operation may be performed on the target page through the preset daemon thread.
Specifically, as shown in fig. 4, it is a flowchart of a specific implementation of S104 in fig. 1 in the first embodiment. As can be seen from fig. 4, S104 includes S1041 to S1042. The details are as follows:
s1041, if the display state of the target page is a display abnormal state, controlling a preset daemon thread to load first target data.
It should be noted that, in the abnormal display state of the target page, normal browsing cannot be performed due to the target page being stuck, and in this situation, the target page needs to be refreshed; the embodiment specifically includes loading, by the preset daemon thread, the first target data used for refreshing the target page.
S1042, restoring the display state of the target page according to the first target data.
Specifically, the target page is refreshed according to the first target data.
Through the analysis, the first target data for refreshing the target page is loaded through the preset daemon thread, the target page with abnormal display is refreshed, and the problem of abnormal page display caused by page jamming can be rapidly solved.
According to the analysis, the page state monitoring method provided by the embodiment of the application monitors the heartbeat logs output by the preset threads for controlling the display of the target page, and determines the display state of the target page according to the monitoring result of the heartbeat logs; and when the display state of the target page is determined to be the display abnormal state, the display state recovery operation is executed on the target page, the display abnormal page can be rapidly and accurately determined, and timely and effective recovery is realized for the display abnormal page.
Further, as shown in fig. 5, it is a flowchart of a specific implementation of S104 in the second embodiment in fig. 1. As can be seen from fig. 5, in this embodiment, compared with the embodiment shown in fig. 4, the specific implementation processes of S501 to 502 are the same as those of S1041 to S1042, but the difference is that S503 to S506 are further included after S502. S503 and S502 are sequentially executed, and are detailed as follows:
s503, monitoring the heartbeat log in a first preset time period.
It is understood that the abnormal display state of the target page may also be due to a program defect of the corresponding browser itself, which may be caused for various reasons, such as memory overflow, limited access devices, system exception, etc., for which the target page needs to be reloaded. Therefore, it may be impossible to make the target page perform a normal display state by refreshing the target page, and in this embodiment, it is further determined whether the target page recovers the normal display state by monitoring the heartbeat log within a first preset time period.
S504, if the heartbeat log is captured in the first preset time period, it is determined that the target page is restored to display a normal state.
It can be understood that, if the display state of the target is abnormal and is caused by the target page being stuck, the target page can be restored to a normal display state by refreshing the target page, and at this time, the heartbeat log is captured within a first preset time correspondingly.
And S505, if the heartbeat log is not captured within the first preset time period, controlling the preset daemon thread to load the second target data, wherein the second target data is used for reloading the target page.
Correspondingly, if the target page is in an abnormal display state, which is not caused by the target page being stuck, the target page cannot be restored to a normal display state by refreshing the target page, and at this time, the heartbeat log cannot be captured within the first preset time period. In this embodiment, the preset daemon thread needs to be further controlled to load the second target data.
S506, reloading the target page according to the second target data.
Because the second target data reloads the target page, if the target page has an abnormal display state caused by a program defect of a corresponding browser, the target page can be restored to a normal display state by reloading the target page through the second target data.
As can be seen from the above analysis, in this embodiment, a preset daemon thread is used to load first target data for refreshing a target page, after a refresh operation is performed on the target page with an abnormal display, if it is determined that the target page is still in an abnormal display state, second target data for reloading the target page is further loaded through the preset daemon thread, and the target page with an abnormal display is reloaded, so that the problem of abnormal page display caused by program defects of a corresponding browser can be quickly solved.
It can be understood that, if the abnormal display state of the target page is not caused by a page jam or a defect of a corresponding browser program, the abnormal display state of the target page cannot be recovered by refreshing the target page or reloading the target page, and at this time, display abnormal state prompt information needs to be sent to a predetermined terminal.
In an alternative implementation manner, as shown in fig. 6, it is a flowchart of a specific implementation of S104 in the third embodiment in fig. 1. As can be seen from fig. 6, in this embodiment, compared with the embodiment shown in fig. 5, the specific implementation processes of S601 to 606 are the same as those of S501 to S506, but the difference is that S607 to S609 are further included after S606. It should be noted that S607 and S606 are in a sequential execution relationship, and are detailed as follows:
s607, monitoring the heartbeat log in a second preset time period.
It can be understood that, if the abnormal display state of the target page is not caused by the program defect of the corresponding browser, the target page cannot be restored to the normal display state by reloading the target page. Correspondingly, the heartbeat log cannot be monitored in a second preset time period, and if the abnormal display state of the target page is caused by the program defect of the corresponding browser, the target page can be restored to the normal display state by reloading the target page. Correspondingly, the heartbeat information is monitored in a second preset time period. Therefore, in the present embodiment, it is determined whether the target page is restored to the display normal state by monitoring the heartbeat log for a second preset time period.
And S608, if the heartbeat log is captured in the second preset time period, determining that the target page is restored to display a normal state.
And S609, if the heartbeat log is not captured in the second preset time period, sending a prompt message of displaying an abnormal state on the target page to a predetermined terminal.
Through the analysis, the heartbeat log is monitored in the second preset time period, the abnormal page display state which cannot be recovered by refreshing the page and reloading can be found in time, the prompt message of the abnormal target page display state is sent to the predetermined terminal in time, operation and maintenance personnel are reminded to recover the abnormal display state in time, and the timeliness of page recovery is improved.
Fig. 7 is a schematic structural diagram of a page status monitoring apparatus according to an embodiment of the present application. As can be seen from fig. 7, the page status monitoring apparatus 7 provided in the embodiment of the present application includes: a loading module 701, a monitoring module 702, a determining module 703 and a recovering module 704. Wherein the content of the first and second substances,
a loading module 701, configured to receive a page loading instruction carrying page attribute information, and load and display a target page based on the page attribute information;
a monitoring module 702, configured to monitor a heartbeat log, where the heartbeat log is output by a preset thread that controls display of the target page;
a determining module 703, configured to determine a display state of the target page based on the heartbeat log;
a restoring module 704, configured to execute a display state restoring operation on the target page if the display state of the target page is a display abnormal state.
In an optional implementation manner, the loading module 701 includes:
the starting unit is used for starting a corresponding browser after detecting a page loading instruction which is triggered by a user and carries page attribute information;
and the first loading unit is used for loading and displaying the target page in the browser based on the page attribute information.
In an optional implementation manner, the display state of the target page includes a display abnormal state and a display normal state;
the determining module 703 includes:
the first determining unit is used for determining that the target page is in an abnormal display state if the heartbeat log is not captured in the current monitoring period;
and the second determining unit is used for determining that the target page is in a normal display state if the heartbeat log is captured in the current monitoring period.
In an alternative implementation, the recovery module 704 includes:
the first control unit is used for controlling a preset daemon thread to load first target data if the display state of the target page is a display abnormal state;
and the restoring unit is used for restoring the display state of the target page according to the first target data.
In an alternative implementation, the first target data is used to refresh the target page;
the recovery unit is specifically configured to:
and refreshing the target page according to the first target data.
In an optional implementation manner, the recovery module 704 further includes:
the first monitoring unit is used for monitoring the heartbeat log in a first preset time period;
a third determining unit, configured to determine that the target page resumes to display a normal state if the heartbeat log is captured within the first preset time period;
the second control unit is configured to control the preset daemon thread to load the second target data if the heartbeat log is not captured within the first preset time period, where the second target data is used to reload the target page;
and the second loading unit is used for reloading the target page according to the second target data.
In an optional implementation manner, the recovery module 704 further includes:
the second monitoring unit is used for monitoring the heartbeat log in a second preset time period;
a fourth determining unit, configured to determine that the target page resumes to display a normal state if the heartbeat log is captured within the second preset time period;
and the sending unit is used for sending prompt information of displaying abnormal states of the target page to a predetermined terminal if the heartbeat log is not captured in the second preset time period.
Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 8, the terminal device 8 of this embodiment includes: a processor 80, a memory 81, and a computer program 82, such as a page status monitoring program, stored in the memory 81 and operable on the processor 80. Processor 80, when executing computer program 82, implements the steps in the various page status monitoring method embodiments described above, such as steps 101-104 shown in FIG. 1.
Illustratively, the computer program 82 may be partitioned into one or more modules/units that are stored in the memory 81 and executed by the processor 80 to accomplish the present application. 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 of the computer program 82 in the terminal device 8. For example, the computer program 82 may be divided into a loading module, a monitoring module, a determining module, and a recovery module (module in the virtual device), each module having the following specific functions:
the loading module is used for receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page;
the monitoring module is used for monitoring a heartbeat log, and the heartbeat log is output by a preset thread for controlling the display of the target page;
the determining module is used for determining the display state of the target page based on the heartbeat log;
and the recovery module is used for executing display state recovery operation on the target page if the display state of the target page is the display abnormal state.
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 application. 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 application.
In the embodiments provided in the present application, 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 communication 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 application 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 in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. . 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 content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 application and are intended to be included within the scope of the present application.
Claims (10)
1. A page state monitoring method is characterized by comprising the following steps:
receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page;
monitoring a heartbeat log, wherein the heartbeat log is output by a preset thread for controlling the display of the target page;
determining a display state of the target page based on the heartbeat log;
and if the display state of the target page is the display abnormal state, executing display state recovery operation on the target page.
2. The method for monitoring page status according to claim 1, wherein after receiving a page loading instruction carrying page attribute information, loading and displaying a target page based on the page attribute information, comprises:
after receiving a page loading instruction carrying page attribute information, starting a corresponding browser;
and loading and displaying the target page in the browser based on the page attribute information.
3. The page status monitoring method according to claim 1 or 2, wherein the display status of the target page includes a display abnormal status and a display normal status;
the determining the display state of the target page based on the heartbeat log includes:
if the heartbeat log is not captured in the current monitoring period, determining that the target page is in an abnormal display state;
and if the heartbeat log is captured in the current monitoring period, determining that the target page is in a normal display state.
4. The page status monitoring method according to claim 3, wherein if the display status of the target page is a display abnormal status, performing a display status recovery operation on the target page, including:
if the display state of the target page is a display abnormal state, controlling a preset daemon thread to load first target data;
and restoring the display state of the target page according to the first target data.
5. The page status monitoring method according to claim 4, wherein said first target data is used for refreshing said target page;
the restoring the display state of the target page according to the first target data includes:
and refreshing the target page according to the first target data.
6. The page status monitoring method according to claim 5, further comprising, after said refreshing said target page according to said first target data:
monitoring the heartbeat log within a first preset time period;
if the heartbeat log is captured within the first preset time period, determining that the target page is restored to display a normal state;
if the heartbeat log is not captured within the first preset time period, controlling the preset daemon thread to load the second target data, wherein the second target data is used for reloading the target page;
and reloading the target page according to the second target data.
7. The page status monitoring method according to claim 6, further comprising, after said reloading said target page according to said second target data:
monitoring the heartbeat log within a second preset time period;
if the heartbeat log is captured within the second preset time period, determining that the target page is restored to display a normal state;
and if the heartbeat log is not captured in the second preset time period, sending prompt information of displaying abnormal states of the target page to a predetermined terminal.
8. A page status monitoring apparatus, comprising:
the loading module is used for receiving a page loading instruction carrying page attribute information, loading a target page based on the page attribute information and displaying the target page;
the monitoring module is used for monitoring a heartbeat log, and the heartbeat log is output by a preset thread for controlling the display of the target page;
the determining module is used for determining the display state of the target page based on the heartbeat log;
and the recovery module is used for executing display state recovery operation on the target page if the display state of the target page is the display abnormal state.
9. A terminal comprising a memory, a processor and a computer program stored in said memory and executable on said processor, characterized in that said processor implements the steps of the page status monitoring method according to any of claims 1 to 7 when executing said 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 page status monitoring method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911410635.8A CN113127239A (en) | 2019-12-31 | 2019-12-31 | Page state monitoring method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911410635.8A CN113127239A (en) | 2019-12-31 | 2019-12-31 | Page state monitoring method, device, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113127239A true CN113127239A (en) | 2021-07-16 |
Family
ID=76770269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911410635.8A Pending CN113127239A (en) | 2019-12-31 | 2019-12-31 | Page state monitoring method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113127239A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112527748A (en) * | 2020-12-24 | 2021-03-19 | 北京百度网讯科技有限公司 | Method, device, equipment and storage medium for analyzing user operation behaviors |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102215215A (en) * | 2010-08-02 | 2011-10-12 | 深圳市深信服电子科技有限公司 | Method for recovering page and electronic terminal |
| CN102779177A (en) * | 2012-06-27 | 2012-11-14 | 优视科技有限公司 | Back-up method, restoring method and device of browse history of browser |
| CN103024038A (en) * | 2012-12-12 | 2013-04-03 | 北京奇虎科技有限公司 | Method and device for browsing webpage |
| CN103167016A (en) * | 2013-01-07 | 2013-06-19 | 北京奇虎科技有限公司 | Browser crash data uploading and processing method and browser crush data uploading and processing device |
| CN103678019A (en) * | 2012-09-17 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Method and device for automatically restoring browser |
| CN103778254A (en) * | 2014-02-24 | 2014-05-07 | 北京国双科技有限公司 | Method, device and system for processing page access data |
| CN106648971A (en) * | 2016-11-11 | 2017-05-10 | 努比亚技术有限公司 | Crash recovery device, terminal and method |
| WO2017219740A1 (en) * | 2016-06-24 | 2017-12-28 | 武汉斗鱼网络科技有限公司 | Method and system for maintaining active user set based on time roulette and page heartbeat |
| CN108255868A (en) * | 2016-12-29 | 2018-07-06 | 北京国双科技有限公司 | Check the method and apparatus linked in website |
| CN109446455A (en) * | 2018-09-14 | 2019-03-08 | 广东神马搜索科技有限公司 | Page processing method and device |
| CN110401580A (en) * | 2019-06-20 | 2019-11-01 | 平安普惠企业管理有限公司 | Webpage status monitoring method and relevant device based on heartbeat mechanism |
| WO2019228034A1 (en) * | 2018-05-30 | 2019-12-05 | 杭州海康威视数字技术股份有限公司 | Method and apparatus for data synchronization |
-
2019
- 2019-12-31 CN CN201911410635.8A patent/CN113127239A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102215215A (en) * | 2010-08-02 | 2011-10-12 | 深圳市深信服电子科技有限公司 | Method for recovering page and electronic terminal |
| CN102779177A (en) * | 2012-06-27 | 2012-11-14 | 优视科技有限公司 | Back-up method, restoring method and device of browse history of browser |
| CN103678019A (en) * | 2012-09-17 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Method and device for automatically restoring browser |
| CN103024038A (en) * | 2012-12-12 | 2013-04-03 | 北京奇虎科技有限公司 | Method and device for browsing webpage |
| CN103167016A (en) * | 2013-01-07 | 2013-06-19 | 北京奇虎科技有限公司 | Browser crash data uploading and processing method and browser crush data uploading and processing device |
| CN103778254A (en) * | 2014-02-24 | 2014-05-07 | 北京国双科技有限公司 | Method, device and system for processing page access data |
| WO2017219740A1 (en) * | 2016-06-24 | 2017-12-28 | 武汉斗鱼网络科技有限公司 | Method and system for maintaining active user set based on time roulette and page heartbeat |
| CN106648971A (en) * | 2016-11-11 | 2017-05-10 | 努比亚技术有限公司 | Crash recovery device, terminal and method |
| CN108255868A (en) * | 2016-12-29 | 2018-07-06 | 北京国双科技有限公司 | Check the method and apparatus linked in website |
| WO2019228034A1 (en) * | 2018-05-30 | 2019-12-05 | 杭州海康威视数字技术股份有限公司 | Method and apparatus for data synchronization |
| CN109446455A (en) * | 2018-09-14 | 2019-03-08 | 广东神马搜索科技有限公司 | Page processing method and device |
| CN110401580A (en) * | 2019-06-20 | 2019-11-01 | 平安普惠企业管理有限公司 | Webpage status monitoring method and relevant device based on heartbeat mechanism |
Non-Patent Citations (1)
| Title |
|---|
| 范建华;宋云波;: "一种基于E-Key及Web页面监控的网站防篡改机制研究", 成都信息工程学院学报, no. 04 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112527748A (en) * | 2020-12-24 | 2021-03-19 | 北京百度网讯科技有限公司 | Method, device, equipment and storage medium for analyzing user operation behaviors |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20140047425A1 (en) | Initiating update operations | |
| US8806235B2 (en) | Display management for multi-screen computing environments | |
| CN107797833B (en) | Interface display method for application program on intelligent equipment | |
| US20120326945A1 (en) | System for switching displays based on the viewing direction of a user | |
| US8839017B2 (en) | Electronic device and method for detecting power statuses of electronic device | |
| CN109726076B (en) | Applet life cycle management method and system | |
| US20140365833A1 (en) | Capturing trace information using annotated trace output | |
| US9164846B2 (en) | Restarting a software system | |
| US11321454B2 (en) | Notice of intrusion into firmware | |
| US20150033134A1 (en) | Visually Depicting Cloud Resource Utilization During Execution Of An Application | |
| CN102369536A (en) | Image display device, image display method, and recording medium | |
| CN112651367A (en) | Method for intelligently monitoring multi-dimensional aviation display screen | |
| US7716504B2 (en) | System for retaining power management settings across sleep states | |
| CN104216802A (en) | Memory database recovery method and device | |
| CN111581021A (en) | Method, device and equipment for repairing application program starting abnormity and storage medium | |
| CN113127239A (en) | Page state monitoring method, device, terminal and storage medium | |
| US20160246658A1 (en) | Acquiring diagnostic data selectively | |
| US10002041B1 (en) | System and method for maintaining the health of a machine | |
| US8949404B2 (en) | Acquiring graphical operating system post-failure screen | |
| KR102137891B1 (en) | Server managing Method, Server, and Recording medium using User Specialized Operating Mechanism on BMC environment | |
| US9542250B2 (en) | Distributed maintenance mode control | |
| CN111427738A (en) | Display method, application monitoring module, bytecode enhancement module and display system | |
| US20220067213A1 (en) | Subliminal Software Detection | |
| US20140059335A1 (en) | Information processing apparatus and activation method | |
| CN116860565A (en) | Abnormality display detection method, abnormality display detection device, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |