Whenever ARES displays the splash screen, the kernel is restarting. Certain events can cause this to happen deliberately (such as when ARES is first unpacked or updated), but most restarts indicate the kernel has crashed.

At present, all known causes of crashing are caused by the kernel running out of memory, especially in configurations with many programs and devices installed simultaneously. Evidence is still being gathered to determine a reliable source of repeated crashes, as the ARES development system is a nearly-maximal configuration with dozens of applications and a full complement of devices that seldom encounters crashes.

If you encounter a kernel crash after teleporting to a new region, please try the following steps:

1. Run the command @input purge to clear out any stuck pipes.
2. If you have the restraint RLV relay installed, run the command @db restraint.session {} to clear any stray session data, and then restart restraint with @reset restraint
3. If the problem reoccurs frequently, submit a deet bug report with the output of the following commands:
   • =ddt e
   • =ddt t
   • @proc tasks detail
   • @device
   • @db security
   • @db menu
   This should give us enough configuration and state information to identify exactly what is going on.