In recent years, I have extensively utilized the resources of the .NET framework to create COM components for VFP to call. However, in the actual usage process, I've found that there are serious memory leak issues when some of these COM components are invoked by VFP. Even after performing numerous operations in VFP to release resources, the situation remains unchanged, which really puzzles me.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP 调用.NET COM 内存泄漏
- Thread starter iswithzhz
- Start date
- Thread starter
- #2
This is not the same issue, but it reminded me of a problem I had years ago.
There was a perplexing issue over a decade ago I had with a VFP app running on a MS server. I never did find out why it wouldn't delete some temp tables and indexes. They would accumulate on the server until all storage was consumed. I did several rewrites of the tables, even testing whether the deletion worked and if not, then trying to delete again. Still didn't delete. Never figured out why. I ended up having to log onto the server and mass deleting the tables every few days before they accumulated enough to use up all the storage space.
There was a perplexing issue over a decade ago I had with a VFP app running on a MS server. I never did find out why it wouldn't delete some temp tables and indexes. They would accumulate on the server until all storage was consumed. I did several rewrites of the tables, even testing whether the deletion worked and if not, then trying to delete again. Still didn't delete. Never figured out why. I ended up having to log onto the server and mass deleting the tables every few days before they accumulated enough to use up all the storage space.
