Jojakim Stahl wrote:
<<
still no solution. Running since last Friday, fbserver.exe grew up to
+3GB memory so far. Few minutes ago, I stopped all our services, it
remained only one attachment from isql to select mon$memory_usage:
memory did not went down. IMHO, this memory leak is not caused by a
client leaving open something, otherwise the memory should go down
when the connection is closed, shouldn't it?

>>

Could it be that the "only one attachment remained" is a cause of
your problems? If the transaction is not R/O+committed it could
prevent moving the transaction counters.

--
Aage J.