< Cracking | Knowledge Base | Cron >
This is about the term crash, as used in vernacular computing terminology. Strictly speaking, "Crash", refers to a Head crash of a hard disc. However the term is now used generically to refer to any condition in which a process ceases responding or dies abnormally.
See also: Common Problems and Reporting A Problem
A "crash" is a condition in which a process completely stops responding or exits abnormally. It is a type of error or "exception", that is a circumstance which differs from what was expected to occur.
Crashes can be caused by numerous causes. Different processes may spiral out of control while accidentally fighting for control of the same resource, there could be a bug or incompatibility in the program code or there could be a hardware problem. In very rare cases there could be an internal problem with the kernel
Whatever the cause, a Crash is usually detected by the desktop environment and reported by a dialog box, typically saying "this window is not responding" or "this application has crashed" or similar language. In cases where the window remains open, and the process continues to run, but has stopped responding, the window manager will offer to kill the process.
Processes can also be killed manually by pressing ctrl alt esc and clicking the offending window, or by using the task manager, or the kill and killall commands on the command line.
If a crash occurs regularly or interrupts work, please file a PR.

< Cracking | K.B. Index | Cron >
This is an article from the Knowledge Base, a project of the Vistua Online Helpdesk to form a body of articles relating to common system topics. You are welcome to contribute to it.