If you are experiencing problems, here are some things you can try:
This is usually caused by filling up object space so much that the OS cannot allocate more memory for objects. This may be because you needed to run a garbage collection before object space grew to this point. This can happen right now because the full garbage collector does not run automatically in the implementation right now, unfortunately. It can be invoked from the UI from the "System/Object Memory/Collect Garbage" menu item on the launcher, or programmatically by calling "VM collectGarbage".
This happens when the system runs out of space for compiled code, which is held in a memory area whose size is fixed at system startup. You can change the size of this area by changing the CodeSize parameter in the Strongtalk startup options file, .strongtalkrc. The code size is specified in kilobytes. 6000kb is usually plenty big enough. The startup options do not take effect until the next session.
This error has been seen in the past due to some unknown bug, probably a deadlock of some kind in the UI. We think that this bug has been eliminated, but if you encounter it, it often clears up on its own if you wait a bit or move the mouse over the window and other windows, and then try clicking a few times on various windows.
Other kinds of system crashes (other than stack overflows) usually are caused by some other bug in the native code compiler, which have not all been worked out. These are often hard to reproduce, so just trying the operation again after restarting may work. If it happens repeatedly and you need to make the system more stable, you can try the following steps: