One of the most popular browsers billion users have installed on their devices is Google Chrome. Its many features and the user-friendly look is part of why we like the browser. And even though it is in the list of the top browsers, we can all agree that it does have its issues.
Take for instance the infamous ‘Aw, Snap!’ page, which is displayed whenever a page crashes but doesn’t inform users about the issue that it has encountered.
If you want to troubleshoot the error, you cannot do it since there is no error code you can follow to find out the answer to why a certain page can’t be displayed. Here’s where Google is making this issue easier to solve.
Chrome Will Add Error Codes to The Crash Page
Chrome Devs are now working on making debugging crashes easier by adding error codes. basically, they’re similar to the ones we see on the Windows blue screen of death (BSOD) crash pages.
Chrome users will be able to use that code and search for it online to find ways of debugging certain types of crashes.
The feature has been added in Chrome Canary (v81) releases for testing. Google has explained this change in a commit with the title “Show crash exit code on sad tab page,” explaining that it will “aid in the troubleshooting of crashed tabs, display the renderer process’ exit code on the sad tab page.”
Users can test the look of these error codes by opening Chrome Canary and navigating to:
chrome://crash or chrome://kill
These searches will trigger a tab crash that reveals the message “Error code: RESULT_CODE_CRASHED” or “Error code: RESULT_CODE_KILLED”.
You can find here all the 137 error codes that have been configured in Chrome so far. While this feature is being tested in Chrome v81, we don’t know if it will show up when Chrome 81 rolls out, but what we do know is that it will be released in the future and should also be available on all the Chromium-based browsers – such as Brave, Opera, or Vivaldi.