Jump to content
Monte Carver

Memory Leak after FireDAC loses DB connection

Recommended Posts

While using a TFDConnection (FireDAC) our application leaks memory after the DB connection is lost.  The size of the leaks is directly related to how many TFDQuery instances have been instantiated.  Please advise how to resolve these relatively massive leaks.  Incidentally this is running against a DB2 database

Edited by Monte Carver

Share this post


Link to post

there are many variants to think about:

  • do you try to "close" the FDQry when "lost connection" is noticed?
  • if, your FDQry are being used to run tasks on threads, for example? ...threads need to be notified in case of connection loss and stop any actions related to them!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×