Sorry for not using Mantis I am at home at the moment and don't have my access details.
Active4D is not fully deallocating memory when sessions timeout. When a session times out then Active4D is not always de-allocating memory. I said not always because the next one or two requests seem to use a piece of the previously allocated memory, but if another request comes in then memory is allocated and not de-allocated when the Sessions timeout. The net result is that the allocated pool of memory slowly creeps up. After about 20 requests the server had lost about 1 Meg memory. Has anybody else noticed this? Michael Bond
