Thanks for your input, Peter. Actually you're right, the app running as a service frees memory but in a strange way: it doesn't immediately give it out to the pool but when another service needs memory it is released to a certain extent so as it can be "torn off by the crowd". What I'm afraid of is that some programs may not know if that partly released memory (or signed to future release) is for reuse...

I don't understand why the memory is not released immediately. While I've scanned a text file and FCLOSED it the memory should be returned to the pool which is not the case at all.

Przemek