Google is working on integrating error codes on error pages that the Chrome web browser displays when something goes wrong.
Google Chrome, like any other desktop browser, displays error pages when things go wrong. Error pages may be displayed if connections to sites cannot be established, when a tab crashes, or when there is a problem with the security of the connection.
The error pages may provide information on the error but that is not always the case. The dreaded Aw, Snap, "Something went wrong while displaying this webpage" for example does not reveal any useful information.
It is up to the user to figure out what happened and how to resolve the issue.
Google has implemented a change in the latest Chrome Canary version that may improve error troubleshooting. The browser displays an error code on the error page that may provide further information on the issue or may be of assistance when someone else is looking at fixing the issue.
The error code is displayed underneath the error message. Chrome users may load chrome://kill, an internal page that simulates an error, to see how it looks.
Not all error codes may reveal actionable information. While error codes such as "out of memory", "wait timeout", or "result code hung" may be useful, there are error codes such as "SIGFPE", "SBOX_FATAL_MITIGATION", or "STATUS_CALLBACK_RETURNED_WHILE_IMPERSONATING" that most users won't find helpful at all.
The entire list of error code strings is available on the Chromium website. A public list of descriptions or explanations for each of the error codes is not available at the time of writing.
Chromium users may load chrome://crash/ to display a list of recent crashes of the web browser.
It is unclear at the time of writing if all or most Chromium-based web browsers will follow Google's lead and display the error codes. Some, like the Canary version of the Chromium-based Microsoft Edge web browser, already display these codes as well.
Additional information about errors and issues that help troubleshoot problems are always welcome. The error codes that Chrome will display are for the most part not helpful to home users who try to find out why something did not work out as expected.
It may help support engineers and people on Google's official support forum when it comes to figuring out why something produced an error.
Now you: what is your take on these error codes? Good mode or not useful at all? (via Deskmodder)Advertisement
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.