Mac OS X: Classic Quits Unexpectedly or Stops Responding ("Freezes")

Classic may quit unexpectedly or stop responding to input (a "freeze"). Use this document to troubleshoot the issue.
Note: This technical document covers one aspect of troubleshooting the Classic environment. For more information, see "Mac OS X: Troubleshooting the Classic Environment"

Symptom

You may receive an alert box with this error message:

If you have this message, stop here and go to "Mac OS X 10.1: 'The Classic Environment is Not Responding' Message".

These signs indicate that Classic has quit:

These signs indicate that Classic is running but not responsive:


Solution

Quit the nonresponsive Classic application or environment

Choose Force Quit from the Apple Menu or use the Command-Option-Escape key combination to access the Force Quit dialog box.

Note: With Mac OS X 10.1.3, you can force quit individual Classic applications. With Mac OS X 10.1.2 and earlier, force quitting has the same effect as force quitting the entire Classic environment.

Determining the cause

An extensions conflict may contribute to undesirable behavior in Mac OS 9 or the Classic environment. You should first try extensions troubleshooting. For information on extensions troubleshooting, see:

106679: "Mac OS X: Classic Will Not Finish Starting Up - Extensions Conflict or 'Bus Error'"
30929: "Mac OS: Extension Conflict Troubleshooting/Extensions Manager Features"

If extensions troubleshooting does not resolve the issue, some files or system software may have been damaged become unusable. This may happen over time, particularly if the computer has often been improperly shut down or improperly restarted.
Published Date: Oct 7, 2016