Process control method, device and system for abnormal page

Abstract

The invention provides a method and a device for controlling processes of abnormal pages. The method comprises the following steps: acquiring a page address list of the abnormal pages, wherein the abnormal pages comprise pages which cause a browser to be broken down and / or jammed; judging whether a page address which a user requests to access is in the page address list; and if yes, creating a page independent subprocess by a browser host process and rendering a page corresponding to the page address which the user requests to access by the page independent subprocess. According to the invention, the normal use of the browser can be protected from influences when the user accesses the high risk page.

Description

technical field [0001] The invention relates to the field of data processing, in particular to a process control method, device and system for abnormal pages. Background technique [0002] The browser kernel is also the rendering engine used by the browser. The rendering engine determines how the browser displays the content of the webpage and the format information of the page. The kernel of the current browser is multi-threaded, and they cooperate with each other under the control of the kernel. To maintain synchronization, a browser implements at least the following three resident threads: [0003] 1. Javascript engine thread (referred to as JS thread) is based on event-driven single-threaded execution. The JS engine has been waiting for the arrival of tasks in the task queue and then processing them; [0004] 2. The GUI (Graphical User Interface, Graphical User Interface) rendering thread is responsible for rendering the browser interface. When the interface needs to be...

AI Technical Summary

Problems solved by technology

[0006] At present, the Internet is highly developed, various webpages emerge in endlessly, and webpage development engineers are also uneven. Some webpages improperly use JS, Flash and other technologies when designing, and only unilaterally realize the web requirements. Incompatibility, and strict compatibility testing was not carried out afterwards, so a large number of web pages incompatible with browsers appeared. Such pages that easily cause browser crashes or freezes are called high-risk pages.

[0007] For example, the infinite loop of JS scripts in webpage A, occupying the CPU for a long time will suspend the GUI update of the browser, and the subsequent event responses will also be queued and cannot be processed, thus causing the browser to fail to respond to users The operation is stuck; for another example, the JS script in web page B performs a large number of DOM operations. Once the JS call ends, it will immediately perform a GUI rendering, and then start the next task, so a large number of DOM operations in JS are also It will cause the event response to be slow or even really freeze the browser

Another example is that the Flash AS script in webpage C falls into an infinite loop, which leads to the exhaustion of system resources and the browser freezes.

Accessing such pages can easily cause the browser to crash and freeze, making the entire browser unusable

Images