Does the Spyder kernel status indicator accurately reflect state after fatal script crashes?

Spyder utilizes a kernel status indicator to signal whether the IPython console is currently executing code or is idle. While standard execution flows transition the indicator correctly, there is an observed inconsistency during fatal script crashes.

In certain crash scenarios, the indicator may remain in a 'Busy' state despite the kernel no longer processing instructions. This creates ambiguity regarding whether the environment is truly hung or if the IDE has simply failed to receive the termination signal from the backend.

What mechanisms determine the transition from 'Busy' to 'Idle' during an unhandled fatal exception? Is there a configuration to force a status refresh when the kernel becomes unresponsive?