This happens, when the aolserver reaches the 2GB frontier. Daily reboots are still a good advice. needed memory relates directly to the number of connection threads, since every connection thread has its own tcl interpreter and own copy of the procs of the blueprint). memory consumption goes down, when e.g. not used packages are not installed, or when the number of connection threads is reduced. another option to reduce the memory needed is to you ttrace (distributed with libthread), which creates tcl procs on demand via Tcl's unknown handler.
