Running gbak will cause the process to continuously use more memory.
Type of data, db scheme, or any other variable like that doesnt seem to affect this behaviour.
As long as its running, it will consume more and more memory, as if memory was leaking.
Ive tried to gbak with -g and without -g, and the results are the same.
This behaviour is making it impossible for us to backup large dbs, since eventually their gbak will consume all memory available and the server stops responding properly to requests.
Ive been using firebird for about 6 years and never had that problem before. We just switched datacenters, from an identically configured machine, which is why this boggles me so much.