Firebird keeps increasing memory usage until client disconnects?


This is usually a symptom of transaction handles not being released after the transaction is over. If you are programming the Firebird C API directly, check your code. Otherwise, it might be a bug in the connectivity library you use.

When you create a new transaction handle, Firebird allocates some memory to hold information about the transaction and keeps it allocated until you release the handle. When you disconnect, all handles related to that connection are released automatically.

A similar problem can also happen with statement handles not being properly released.


Do you find this FAQ incorrect or incomplete? Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird databases), before it enters the main FAQ database. If you desire so, the changes will be credited to your name. To learn more, visit our add content page.

If you are a commercial tool maker and your tool features a great way to handle the issue written about in this FAQ, please check out our advertisement page.



All contents are copyright © 2007-2017 FirebirdFAQ.org unless otherwise stated in the text.


Links   Firebird   News   FlameRobin   Home Inventory powered by FB  
Add content   Advertise   About  

Categories
 Newbies
 SQL
 Installation and setup
 Backup and restore
 Performance
 Security
 Connectivity and API
 HOWTOs
 Errors and error codes
 Miscellaneous