hwajungle.blogg.se - Cara mengatasi google chrome not responding windows 10

Newer versions might have slightly different steps. Please note that these instructions were written with Safari 7 as the version used. If this happens on your site, look for the "XHRs" folder for the Ajax requests. Note that on pages with a large number of resources, Safari will group the resources by type into folders.

Safari will show detailed information about the request. Locate the Ajax request that has been made to the server and click it.

Safari will show a list of all resources (images, scripts etc) which have been loaded for the page.

Reload the page so Safari can capture all network requests.

Additional information can also be found in the Resources tab.

Safari logs general Ajax errors to the developer console - in the example shown above a 404 Not Found error.

Any errors encountered on the page are shown in the developer console.

The developer console will show at the bottom of the page.

Select the Show Error Console option from the Develop menu.

Close the preferences - the Develop menu will now be shown.

Check the box for Show Develop menu in menu bar option.

Click the Advanced tab in the Preferences window.

Enable the developer menu in the Advanced tab.

Open the Safari menu and select Preferences.

If you don't have a Develop menu shown in Safari it needs to be enabled.

By default Safari hides its built-in developer tools.

Instructions on how to do this with your browser are shown below. Modern browsers all come with built in developer tools, which can be used to find out what data the server is responding to the DataTables Ajax request with.

So discovering what that reply was will be the starting point for resolving the issue full. If the server didn't reply to the Ajax request with a 2xx status code, we need to know what it did reply with, so we can take corrective action.

This error (7) indicates a general error, as stated above. For example the server might respond with 404 Not Found indicating that the file requested is not available at the given URL, or 500 Internal Error which indicates that the server encountered an error while processing the request.ĭataTables will fire a specific error for the case where the request from the server is a valid return ( 200 Ok for example), but not valid JSON - see technical note 1 for more information. This occurs when jQuery falls into its error callback handler (this callback built into DataTables), which will typically occur when the server responds with anything other than a 2xx HTTP status code. The error given is:ĭataTables warning: table id= is the DOM id of the table that triggered the error. When using the ajax option to load data for DataTables, a general error can be triggered if the server responds with anything other than a valid HTTP 2xx response.