We've recently learned a lot about memory leaks in TClientDataSet. As these appear to have been around for a long time, I wonder whether we are simply among the last to discover them? They seem to make use of the TClientDataSet for any but transient operations a very poor choice. And the memory issues seem not to be true leaks, but rather ever increasing memory allocations until the CDS is destroyed.
We've recently learned a lot about memory leaks in TClientDataSet. As these appear to have been around for a long time, I wonder whether we are simply among the last to discover them? They seem to make use of the TClientDataSet for any but transient operations a very poor choice. And the memory issues seem not to be true leaks, but rather ever increasing memory allocations until the CDS is destroyed.
David Heffernan I agree, but I explained the detail because I do not usually see that leaked memory is recovered.
ReplyDeleteSorry I don't have a solution for this issue, but your post provoked me me to find out if the Midas source is shipped or not, and it appears that it does (https://stackoverflow.com/questions/36336870/where-can-i-find-midas-library-source-code), but no idea as to how to debug and rebuild it.
ReplyDeletestackoverflow.com - Where can I find MIDAS library source code?
Edwin Yip The source is there, but we see the problems in two much different vintages. As no one seems to have been concerned to resolve the problems, we are more likely to remove the ClientDataset from our products. We have tested FireDac, and it does not have these issues, that is likely to be the choice for new work.
ReplyDelete