Home/ Questions/Q 1019151
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T10:58:02+00:00

I am combating some memory issues in my app and am finally managing to

  • 0

I am combating some memory issues in my app and am finally managing to get to the bottom of it. I have had an example recently where my process memory went up to 800mb when processing a task. I have managed to get this to settle at 140mb now which is perfectly acceptable. However this has made me question my understanding of the .NET Garbage Collector. My memory issue was fixed by freeing 2 non .NET objects (TADOCommand and TDataSet – in delphi) after every use. The scope of these variables are local to the procedure so I presumed they should be cleared up automagically because nothing should have a reference to them.

So, how does .NET handle freeing objects that are not .NET? Or doesn’t it?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It doesn’t. The .NET Garbage Collector only handles managed objects. Everything else must be cleaned up by something else.

    If said resources are encapsulated by managed types, you can use IDisposable to implement the cleanup.

    • 0