 | This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Crash-only software" – news · newspapers · books · scholar · JSTOR (August 2013) (Learn how and when to remove this message) |
A crash-only software is a computer program that handle failures by simply restarting, without attempting any sophisticated recovery. Correctly written components of crash-only software can microreboot to a known-good state without the help of a user. Since failure-handling and normal startup use the same methods, this can increase the chance that bugs in failure-handling code will be noticed, except when there are leftover artifacts, such as data corruption from a severe failure, that don't occur during normal startup.
Crash-only software also has benefits for end-users. All too often, applications do not save their data and settings while running, only at the end of their use. For example, word processors usually save settings when they are closed. A crash-only application is designed to save all changed user settings soon after they are changed, so that the persistent state matches that of the running machine. No matter how an application terminates (be it a clean close or the sudden failure of a laptop battery), the state will persist.
See also
References
- Candea, George; Fox, Armando (May 2003). "Crash-only software". 9th Workshop on Hot Topics in Operating Systems. Lihue, Hawaii, USA.
External links
 | This software-engineering-related article is a stub. You can help Misplaced Pages by expanding it. |