This chapter (really just a fairly random collection of notes at the moment) is simply designed to help with some of the more frustrating prolems you may have when using TkHol.
Apologies in advance.
TkHol works much better with an advanced window manager such as fvwm or mwm, instead of twm. You should endeavour to have fvwm or something similar installed and maintained on your system. It's free, robust, and available from all good ftp sites. You should also take the time to configure your window manager so you find it is easy to manipulate and find iconified windows. If you don't do this you will get frustrated with modern windowing applications very quickly!
When SML processes loop and run out of memory, they may well just fall over with a core dump. This is really bad. Command line users usually notice the looping well before the core dump occurs, but with a graphical tool people tend not to intervene with a Ctrl-C quickly enough.
So what I've done (a really gross hack) is to treat NJSML heap expansion messages as special, and watch if the heap expansion seems to be going out of control. There is a threshold which is one of the database parameters - initially I set this to 70MB since that is about how big a process grows on our machines here at Cambridge before it dies.
You may set this option from the ``Communicating with ML'' menu of the Options menu.