CN113127239A - Page state monitoring method, device, terminal and storage medium - Google Patents

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

Method, device, terminal and storage medium for monitoring page status

technical field

The present application belongs to the field of computer technology, and in particular, relates to a method, device, terminal and storage medium for monitoring page status.

Background technique

At present, when the browser page loads too much content, or the browser page needs to perform high-intensity calculations, it is easy to crash the page. However, because the browser page itself is running in sandbox mode, page repair cannot be performed in a timely and effective manner when a crash occurs.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present application provide a method, device, terminal, and storage medium for monitoring a page state, so as to solve the problem that page repair cannot be performed in a timely and effective manner in the prior art.

A first aspect of the embodiments of the present application provides a far page status monitoring method, including:

receiving a page loading instruction carrying page attribute information, and loading and displaying a target page based on the page attribute information;

The heartbeat log is monitored, and the heartbeat log is output by a preset thread that controls the display of the target page;

Determine the display state of the target page based on the heartbeat log;

If the display state of the target page is an abnormal display state, a display state restoration operation is performed on the target page.

In an optional implementation manner, after receiving the page loading instruction carrying the page attribute information, loading and displaying the target page based on the page attribute information, including:

After receiving the page loading instruction carrying the page attribute information, start the corresponding browser;

The target page is loaded and displayed 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 within the current monitoring period, it is determined that the target page is in an abnormal state;

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 an optional implementation manner, if the display state of the target page is an abnormal display state, performing a display state restoration operation on the target page, including:

If the display state of the target page is an abnormal display state, controlling the preset daemon thread to load the first target data;

The display state of the target page is restored according to the first target data.

In an optional implementation manner, 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:

The target page is refreshed according to the first target data.

In an optional implementation manner, after 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, it is determined that the target page is restored to display a normal state;

If the heartbeat log is not captured within the first preset time period, the preset daemon thread is controlled to load the second target data, and the second target data is used to reload the target page;

The target page is reloaded according to the second target data.

In an optional implementation manner, after 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, it is determined that the target page is restored to display a normal state;

If the heartbeat log is not captured within the second preset time period, a prompt message that the target page displays an abnormal state is sent to a predetermined terminal.

A second aspect of the embodiments of the present application provides a device for monitoring page status, including:

a loading module, configured to receive a page loading instruction carrying page attribute information, load and display a target page based on the page attribute information;

a monitoring module for monitoring a heartbeat log, the heartbeat log being output by a preset thread that controls the display of the target page;

a determining module, configured to determine the display state of the target page based on the heartbeat log;

A restoration module, configured to perform a display state restoration 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 includes:

a startup unit, configured to start a corresponding browser after detecting a page loading instruction that carries page attribute information triggered by a user;

A first loading unit, configured to load and display 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:

a first determining unit, configured to determine that the target page is in a display abnormal state if the heartbeat log is not captured in the current monitoring period;

The second determining unit is configured to determine 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, the recovery module includes:

a first control unit, configured to control a preset daemon thread to load the first target data if the display state of the target page is an abnormal display state;

A restoring unit, configured to restore the display state of the target page according to the first target data.

In an optional implementation manner, the first target data is used to refresh the target page;

The recovery unit is specifically used for:

The target page is refreshed according to the first target data.

In an optional implementation, the recovery module further includes:

a first monitoring unit, configured to monitor the heartbeat log within a first preset time period;

a third determining unit, configured to determine that the target page is restored to display a normal state if the heartbeat log is captured within the first preset time period;

a second control unit, 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, and the second target data is used for reloading the target page;

A second loading unit, configured to reload the target page according to the second target data.

In an optional implementation, the recovery module further includes:

a second monitoring unit, configured to monitor the heartbeat log within a second preset time period;

a fourth determining unit, configured to determine that the target page is restored to display a normal state if the heartbeat log is captured within the second preset time period;

A sending unit, configured to send, to a predetermined terminal, prompt information that the target page displays an abnormal state if the heartbeat log is not captured within the second preset time period.

A third aspect of an embodiment 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, wherein the processor executes the computer program When implementing the steps of the page state monitoring method described in the first aspect above.

A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein when the computer program is executed by a processor, the page state described in the first aspect above is implemented The steps of the monitoring method.

Compared with the prior art, the page state monitoring method provided by the embodiment of the present application has the beneficial effect of monitoring the heartbeat log output by the preset thread displayed on the control target page, and determining the target according to the monitoring result of the heartbeat log. The display state of the page; and when it is determined that the display state of the target page is an abnormal display state, the display state recovery operation is performed on the target page, which can quickly and accurately determine the display abnormal page, and realize the timely and effective recovery of the abnormal display page. .

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only for the present application. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is the realization flow chart of the page state monitoring method provided by the embodiment of the present application;

Fig. 2 is the concrete realization flow chart of S101 in Fig. 1;

Fig. 3 is the concrete realization flow chart of S103 in Fig. 1;

Fig. 4 is the specific realization flow chart of S104 in Fig. 1 in the first embodiment;

Fig. 5 is the specific realization flow chart of S104 in Fig. 1 in the second embodiment;

Fig. 6 is the concrete realization flow chart of S104 in Fig. 1 in the third embodiment;

7 is a schematic structural diagram of a device for monitoring page status provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

In the following description, for the purpose of illustration rather than limitation, specific details such as a specific system structure and technology are set forth in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be practiced in other embodiments without 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-intensity calculations, the browser page runs for a period of time due to loopholes in the design of the program that controls the browser page and the stability of the browser itself. Then the page crashes. The browser page itself runs in the sandbox mode. Once the page crashes, the problem cannot be found in time and effectively, and the page can be restored for the problem, resulting in some pages that need to run stably for a long time, such as outdoor advertising screens, in order to To ensure the effect of use, we usually choose to use desktop client programs or native visualization programs. However, desktop clients and native visualization programs have poor cross-platform performance, high development costs, inconvenient secondary development, and slow real-time updates. The problem.

In view of this, the present application proposes a page status monitoring solution, which can restore abnormally displayed pages in a timely and effective manner, and solve the problem that browser pages cannot run stably for a long time.

In order to illustrate the technical solutions described in the present application, the following specific embodiments are used for description. As shown in FIG. 1 , it is an implementation flowchart of the page state monitoring method provided by the embodiment of the present application. This embodiment may be implemented by hardware or software of a page state monitoring device, where the page state monitoring device is a terminal device with a computing function, such as an outdoor display device. Details are as follows:

S101: Receive a page loading instruction carrying page attribute information, and load and display a target page based on the page attribute information.

Understandably, 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 directly sent by the user and other terminal devices. The page attribute information is preconfigured attribute information including basic display information such as the width and height of the page, and the access address of the page.

After receiving the page loading instruction, the current terminal device loads the corresponding target page based on the access address of the page, and displays it according to the basic display information of the page.

In an optional implementation manner, as shown in FIG. 2 , it is a specific implementation flowchart of S101 in FIG. 1 . It can be seen from FIG. 2 that S101 includes S1011 to S1012. Details are as follows:

S1011, after receiving the page loading instruction carrying the page attribute information, start the corresponding browser.

It should be noted that, in an optional implementation manner, a fixed browser is pre-installed on the terminal device, and the browser can usually support Microsoft Windows 7, Server 2008, macOS, Linux, SmartOS, IBM AIX And systems such as FreeBSD, such as Google Chrome, and deploy a js interface package that operates the browser on the terminal device, such as puppeteer.

After receiving the page loading instruction carrying the page attribute information, start the browser through the corresponding js interface package, for example, start Google Chrome through puppeteer.

S1012: Load and display the target page in the browser based on the page attribute information.

Understandably, after the browser is started, the browser enters the target page that needs to be rendered and displayed according to the page attribute information, so as to load and display the target page in the browser.

It can be seen from the above analysis that in this embodiment, by starting the corresponding browser, 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 can be controlled conveniently. page to operate.

S102, monitor a heartbeat log, where the heartbeat log is output by a preset thread that controls the display of the target page.

It should be noted that when the target page is loaded in the browser, a preset thread is configured for the target page, and the preset thread is used to control the display of the target page and is based on a preset heartbeat. The log output logic outputs the heartbeat log. For example, the preset heartbeat log output logic includes preconfiguring a heartbeat log package for the preset thread. If the preset thread is controlled in the process of displaying the target page, monitoring is not To the abnormal display state, the heartbeat log is periodically output based on the heartbeat log package or the heartbeat log is continuously output based on the heartbeat log package; if the preset thread is in the process of controlling the display of the target page, it monitors abnormal display state, the preset thread will not output the heartbeat log. S103: Determine the display state of the target page based on the heartbeat log.

The analysis of S102 shows that when the target page displays a normal state, the preset thread outputs a heartbeat log based on the preset heartbeat log output logic, and when the target page displays an abnormal state, the preset thread does not output a heartbeat Therefore, the terminal device can determine the display state of the target page based on the heartbeat log.

It should be noted that the display state of the target page includes a display abnormal state and a normal display state; in an optional implementation manner, as shown in FIG. 3 , it is a specific implementation flowchart of S103 in FIG. 1 . It can be seen from FIG. 3 that S103 includes S1031 to S1032. Details are as follows:

S1031, if the heartbeat log is not captured in the current monitoring period, determine that the target page is in an abnormal display state.

According to the preset heartbeat log output logic, in the process of controlling the display of the target page by the preset thread, if a display abnormality is detected, 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 a display abnormal state.

S1032, if the heartbeat log is captured in the current monitoring period, determine that the target page is in a normal display state.

The same as above, according to the preset heartbeat log output logic, in the process of controlling the display of the target page by the preset thread, if it is detected that the display of the target page is normal, 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.

According to the above analysis, according to whether the heartbeat log is captured in the current monitoring period, the display state of the target page can be determined, whether the target page is abnormal can be quickly and accurately monitored, and timely early warning and repair can be realized.

S104, if the display state of the target page is an abnormal display state, perform a 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 an abnormal display state, a preset daemon thread can be used to perform display state recovery on the target page operate.

Specifically, as shown in FIG. 4 , it is a flow chart of the specific implementation of S104 in FIG. 1 in the first embodiment. It can be seen from FIG. 4 that S104 includes S1041 to S1042. Details are as follows:

S1041 , if the display state of the target page is an abnormal display state, control a preset daemon thread to load the first target data.

It should be noted that the abnormal display state of the target page may be caused by the target page being stuck, resulting in failure to browse normally. In this case, the target page needs to be refreshed; It is assumed that a daemon thread loads the first target data for refreshing the target page.

S1042. Restore 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.

It can be seen from the above analysis that in this embodiment, the preset daemon thread is used to load the first target data for refreshing the target page, and the refresh operation is performed on the abnormally displayed target page, which can quickly solve the problem caused by the page being stuck. Page abnormal display problem.

It can be seen from the above analysis that the method for monitoring the page status provided by the embodiment of the present application monitors the heartbeat log output by the preset thread that controls the display of the target page, and determines the display status of the target page according to the monitoring result of the heartbeat log; and When it is determined that the display state of the target page is an abnormal display state, performing a display state recovery operation on the target page can quickly and accurately determine the abnormal display page, and realize timely and effective recovery of the abnormal display page.

Further, as shown in FIG. 5 , it is a specific implementation flowchart of S104 in FIG. 1 in the second embodiment. It can be seen from FIG. 5 that, compared with the embodiment shown in FIG. 4 , the specific implementation processes of S501-502 and S1041-S1042 are the same in this embodiment, and the difference is that S503-S506 are also included after S502. It should be noted that S503 and S502 are in a sequential execution relationship, and the details are as follows:

S503, monitor the heartbeat log within a first preset time period.

Understandably, the abnormal display state of the target page may also be due to a program defect of the corresponding browser itself. There are many reasons for this situation, such as memory overflow, limited access to the device, system abnormality, etc. The target page needs to be reloaded. Therefore, by refreshing the target page, the target page may not be able to display normally. In this embodiment, the target page is further determined by monitoring the heartbeat log within a first preset time period. Whether to restore the normal display state.

S504, if the heartbeat log is captured within the first preset time period, determine that the target page is restored to display a normal state.

Understandably, if the abnormal display state of the target is caused by the target page being stuck, the target page can be restored to the normal display state by refreshing the target page. The heartbeat log will be captured within a period of time.

S505, if the heartbeat log is not captured within the first preset time period, control the preset daemon thread to load the second target data, where the second target data is used to reload the target page.

Correspondingly, if the abnormal display state of the target page is not caused by the target page being stuck, the target page cannot be restored to the normal display state by refreshing the target page. The heartbeat log will not be captured for a preset period of time. In this embodiment, the preset daemon thread needs to be further controlled to load the second target data.

S506: Reload the target page according to the second target data.

Since the second target data reloads the target page, if the abnormal display state of the target page is caused by a program defect of the corresponding browser itself, reloading the target page through the second target data can make The target page is restored to display a normal state.

It can be seen from the above analysis that in this embodiment, the preset daemon thread is used to load the first target data for refreshing the target page, and after performing the refresh operation on the abnormal target page, if it is determined that the target page is still abnormal If the display state is displayed, the second target data for reloading the target page is further loaded through the preset daemon thread, and the abnormally displayed target page is reloaded, which can quickly solve the program defect due to the corresponding browser itself. The resulting page abnormal display problem.

Understandably, if the abnormal display state of the target page is not caused by a stuck page or a corresponding browser program defect, the abnormality to the target page cannot be realized by refreshing the target page or reloading the target page. To restore the display state, at this time, it is necessary to send the display abnormal state prompt information to a predetermined terminal.

In an optional implementation manner, as shown in FIG. 6 , it is a specific implementation flowchart of S104 in FIG. 1 in the third embodiment. It can be seen from FIG. 6 that, compared with the embodiment shown in FIG. 5, the specific implementation process of S601-606 is the same as the specific implementation process of S501-S506, the difference is that S607-S609 are also included after S606. It should be noted that S607 and S606 are executed sequentially, and the details are as follows:

S607, monitor the heartbeat log within a second preset time period.

Understandably, if the abnormal display state of the target page is not caused by a program defect of the corresponding browser itself, the target page cannot be restored to the normal display state by reloading the target page. Correspondingly, the heartbeat log will not be monitored within the second preset time period. If the abnormal display state of the target page is caused by a program defect of the corresponding browser itself, then by reloading the target page, you can The target page is restored to display a normal state. Correspondingly, the heartbeat information will be monitored within the second preset time period. Therefore, in this embodiment, it is determined whether the target page is restored to a normal display state by monitoring the heartbeat log within a second preset time period.

S608, if the heartbeat log is captured within the second preset time period, determine that the target page is restored to display a normal state.

S609, if the heartbeat log is not captured within the second preset time period, send a prompt message that the target page displays an abnormal state to a predetermined terminal.

It can be seen from the above analysis that by monitoring the heartbeat log in the second preset time period, the abnormal display state of the page that cannot be restored by refreshing the page and reloading can be found in time, and the abnormal display state of the target page can be sent to the predetermined terminal in time. The prompt information of the status reminds the operation and maintenance personnel to restore the abnormal display state in time, and improves the timeliness of page restoration.

FIG. 7 is a schematic structural diagram of a page state monitoring apparatus provided by an embodiment of the present application. As can be seen from FIG. 7 , the page state monitoring apparatus 7 provided by the embodiment of the present application includes: a loading module 701 , a monitoring module 702 , a determination module 703 , and a restoration module 704 . in,

A loading module 701, configured to receive a page loading instruction carrying page attribute information, load and display a target page based on the page attribute information;

A monitoring module 702, configured to monitor a heartbeat log, the heartbeat log being output by a preset thread that controls the display of the target page;

A determination module 703, configured to determine the display state of the target page based on the heartbeat log;

The restoration module 704 is configured to perform a display state restoration 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:

a startup unit, configured to start a corresponding browser after detecting a page loading instruction that carries page attribute information triggered by a user;

A first loading unit, configured to load and display 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:

a first determining unit, configured to determine that the target page is in a display abnormal state if the heartbeat log is not captured in the current monitoring period;

The second determining unit is configured to determine 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 704 includes:

a first control unit, configured to control a preset daemon thread to load the first target data if the display state of the target page is an abnormal display state;

A restoring unit, configured to restore the display state of the target page according to the first target data.

In an optional implementation manner, the first target data is used to refresh the target page;

The recovery unit is specifically used for:

The target page is refreshed according to the first target data.

In an optional implementation manner, the recovery module 704 further includes:

a first monitoring unit, configured to monitor the heartbeat log within a first preset time period;

a third determining unit, configured to determine that the target page is restored to display a normal state if the heartbeat log is captured within the first preset time period;

a second control unit, 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, and the second target data is used for reloading the target page;

A second loading unit, configured to reload the target page according to the second target data.

In an optional implementation manner, the recovery module 704 further includes:

a second monitoring unit, configured to monitor the heartbeat log within a second preset time period;

a fourth determining unit, configured to determine that the target page is restored to display a normal state if the heartbeat log is captured within the second preset time period;

A sending unit, configured to send, to a predetermined terminal, prompt information that the target page displays an abnormal state if the heartbeat log is not captured within the second preset time period.

FIG. 8 is a schematic structural diagram of a terminal device provided by 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 stored in the memory 81 and executable on the processor 80 , such as a page status monitoring program. When the processor 80 executes the computer program 82, the steps in each of the foregoing embodiments of the page status monitoring method are implemented, for example, steps 101 to 104 shown in FIG. 1 .

Exemplarily, the computer program 82 may be divided into one or more modules/units, which are stored in the memory 81 and executed by the processor 80 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 82 in the terminal device 8 . For example, the computer program 82 can be divided into a loading module, a monitoring module, a determination module and a recovery module (modules in a virtual device), and the specific functions of each module are as follows:

a loading module, configured to receive a page loading instruction carrying page attribute information, load and display a target page based on the page attribute information;

a monitoring module for monitoring a heartbeat log, the heartbeat log being output by a preset thread that controls the display of the target page;

a determining module, configured to determine the display state of the target page based on the heartbeat log;

A restoration module, configured to perform a display state restoration operation on the target page if the display state of the target page is a display abnormal state.

Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit, and the above-mentioned integrated units may adopt hardware. It can also be realized in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above-mentioned system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units. Or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple communication units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated modules/units, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the present application can implement all or part of the processes in the methods of the above embodiments, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer When the program is executed by the processor, the steps of the foregoing method embodiments can be implemented. . Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form, and the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable media may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer-readable media Electric carrier signals and telecommunication signals are not included.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the above-mentioned embodiments, those of ordinary skill in the art should understand that: it can still be used for the above-mentioned implementations. The technical solutions described in the examples are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the application, and should be included in the within the scope of protection of this 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.

Images