Google Chrome displays an error page (aka “Sad Tab”) when a page crashes. This page currently does not tell us, users, the reason for a page crash. Google is working on a solution for this.
Update: Now that Microsoft’s Edge browser is also powered by Chromium, these error messages are applicable to Edge as well.
According to a Chromium code commit that we spotted today, Google will soon enhance this error page with error codes. This will make it easy to diagnose these issues. Here is how the bug associated with this feature explains this:
“To make it easier to diagnose user reports of the sad tab, perhaps we could consider putting the crash exit code on the sad tab as we do for SSL errors. Then users can google for the error, we can seed help center pages to help users, everyone wins.” The page also provides some mockups of how this might look like:
Chrome Crash Error Codes
The code change request has a list of error codes as well. Not all errors are self-explanatory and will need additional documentation to understand. As the Help Center team develops new articles explaining these error messages, diagnosing these will become easier.
- HUNG
- KILLED_BAD_MESSAGE
- GPU_DEAD_ON_ARRIVAL
- INVALID_CMDLINE_URL
- BAD_PROCESS_TYPE
- MISSING_DATA
- SHELL_INTEGRATION_FAILED
- MACHINE_LEVEL_INSTALL_EXISTS
- UNINSTALL_CHROME_ALIVE
- UNINSTALL_USER_CANCEL
- UNINSTALL_DELETE_PROFILE
- UNSUPPORTED_PARAM
- IMPORTER_HUNG
- RESPAWN_FAILED
- NORMAL_EXIT_EXP1
- NORMAL_EXIT_EXP2
- NORMAL_EXIT_EXP3
- NORMAL_EXIT_EXP4
- NORMAL_EXIT_CANCEL
- PROFILE_IN_USE
- PACK_EXTENSION_ERROR
- UNINSTALL_EXTENSION_ERROR
- NORMAL_EXIT_PROCESS_NOTIFIED
- INSTALL_FROM_WEBSTORE_ERROR_2
- EULA_REFUSED
- SXS_MIGRATION_FAILED_NOT_USED
- ACTION_DISALLOWED_BY_POLICY
- INVALID_SANDBOX_STATE
- CLOUD_POLICY_ENROLLMENT_FAILED
- DOWNGRADE_AND_RELAUNCH
- SIGQUIT
- SIGILL
- SIGTRAP
- SIGABRT
- SIGBUS (7)
- SIGFPE
- SIGKILL
- SIGBUS (10)
- SIGSEGV
- SIGSYS
- WAIT_TIMEOUT
- SBOX_FATAL_INTEGRITY
- SBOX_FATAL_DROPTOKEN
- SBOX_FATAL_FLUSHANDLES
- SBOX_FATAL_CACHEDISABLE
- SBOX_FATAL_CLOSEHANDLES
- SBOX_FATAL_MITIGATION
- SBOX_FATAL_MEMORY_EXCEEDED
- SBOX_FATAL_WARMUP
- Crashpad_FailedToCaptureProcess
- Crashpad_HandlerDidNotRespond
- Crashpad_SimulatedCrash
- CPP_EH_EXCEPTION
- STATUS_GUARD_PAGE_VIOLATION
- Out of Memory
- FACILITY_VISUALCPP/ERROR_PROC_NOT_FOUND
- FACILITY_VISUALCPP/ERROR_MOD_NOT_FOUND
- STATUS_INVALID_IMAGE_HASH
- STATUS_STACK_BUFFER_OVERRUN
- STATUS_HEAP_CORRUPTION
- STATUS_DLL_INIT_FAILED
- STATUS_CONTROL_C_EXIT
- STATUS_DLL_NOT_FOUND
- STATUS_STACK_OVERFLOW
- STATUS_BAD_IMPERSONATION_LEVEL
- STATUS_PRIVILEGED_INSTRUCTION
- STATUS_INTEGER_OVERFLOW
- STATUS_INTEGER_DIVIDE_BY_ZERO
- STATUS_FLOAT_UNDERFLOW
- STATUS_FLOAT_STACK_CHECK
- STATUS_FLOAT_OVERFLOW
- STATUS_FLOAT_INVALID_OPERATION
- STATUS_FLOAT_INEXACT_RESULT
- STATUS_FLOAT_DIVIDE_BY_ZERO
- STATUS_FLOAT_DENORMAL_OPERAND
- STATUS_ARRAY_BOUNDS_EXCEEDED
- STATUS_INVALID_UNWIND_TARGET
- STATUS_INVALID_DISPOSITION
- STATUS_NONCONTINUABLE_EXCEPTION
- STATUS_ACCESS_DENIED
- STATUS_INVALID_LOCK_SEQUENCE
- STATUS_ILLEGAL_INSTRUCTION
- STATUS_CONFLICTING_ADDRESSES
- STATUS_NO_MEMORY
- STATUS_INVALID_PARAMETER
- STATUS_INVALID_HANDLE
- STATUS_IN_PAGE_ERROR
- STATUS_ACCESS_VIOLATION
- STATUS_SEGMENT_NOTIFICATION
- STATUS_FATAL_APP_EXIT
- STATUS_SINGLE_STEP
- STATUS_BREAKPOINT
- STATUS_DATATYPE_MISALIGNMENT
- unknown
We shall update this article with more details on these error codes as soon as they become available.
Do you think this is a helpful move? Let us know in the comments section.
Source: Gerrit.
Leave a ReplyCancel reply