Skip to main content

Dispose and finalize

Am avut o discutie zilele astea cu un coleg despre Dispose() si Finalize(), despre modul in care se apeleaza cele doua. O sa prezint pe scurt cele doua metode.
Pentru a implementa metoda Dispose() este nevoie sa implementa interfata IDispose(). Aceasta metoda nu primeste nici un parametru. Se apeleaza de catre dezvoltator cand se doreste sa se elibere resurse folosite de aceasta entitate.
Resursele unmanaged sunt eliberate prin intermediul acestei metode si reprezinta reponsabilitatea utilizatorului.
Pana aici totul este destul de clar.
public class ProcessData: IDispose
{
private Stream _fileStream;
//....
public void Dispose()
{
_fileStream.Dispose();
}
}
Inainte sa explic ce face metoda Finalize si de cine este apelata vreau sa explic cum functioneaza pe scurt GC:
  • Cauta toate resursele (obiectele) managed care sunt referite in codul managed;
  • Incearca sa faca Finalize pe obiectele care nu mai sunt referite in cod;
  • Elibereaza obiectele care nu mai sunt referentiate;
  • Elibereaza spatiul din memorie ocupat de acestea;
Metoda Finalize() este apelata de catre GAG si reprezinta procesul in care GC elibereaza resulsele inainte sa distruga instanta unui obiect. Acesta ar trebuii sa elibereze doar resulsele externe care sunt referentiate. Aceasta metoda este apelata in mod automat, nu se poate controla (in general) momentul in care se apeleaza.
Trebuie avut grija cand se implementeaza aceasta metoda deoarece ordinea in care care se apeleaza Finalize() nu poate sa fie controlata.
Cea ce este bine de stiut, este ca in momentul in care se implementeaza Finalize() si Dispose() se recomanda ca Finalize() sa execute si codul care apare in Dispose(). GC nu o sa apeleze niciodata Dispose().
Totodata metoda Finalize() trebuie sa apeleze obligatoriu base.Finalize(), recomanda intr-un bloc finnaly:
protected override void Finalize()
{
try
{
//Code Cleanup
}
finally
{
base.Finalize();
}
}
Urmatoarele reguli trebuie respectate cand se implementeaza Finalize():
  • Trebuie sa fie mereu protected;
  • Trebuie sa apeleze base.Finalize();
  • Trebuie sa elibere resursele unmanaged;
  • .NET nu garanteaza ca Finalize() se va executa pentru fiecare instanta separat intr-un anumit moment;
  • Nu faceti new aceasta metoda;
  • Nu aruncati exceptii din Finalize();
  • Nu il definiti in date de tip value type;
  • Nu implementati Finalize() cu body gol, deoarece se consuma resurse fara rost;
Acest mecanism trebuie sa fie considerat un mecanism de fallback. Pentru eliberea resurselor se recomanda sa se folosesca Dispose(), iar Finalize() sa apeleze la randul lui codul care se executa in Dispose().
Dar Dispose() nu face release la obiect. In cazul in care dispose-ul elibereaza resursele, atunci nu mai este nevoie sa executam si Finalize(). Pentru a spune la GC sa nu mai ruleze Finalize() trebuie sa scriem urmatoarea linie de cod in metoda Dispose():
GC.SuppressFinalize(this).
Mai jos gasiti un exemplu cum sa se apeleze Dispose():
class StoreManager: IDisposable
{
private bool isDisposed = false;

~StoreManager: ()
{
Dispose(false);
}

protected void Dispose(bool disposing)
{
if (disposing)
{
// Dispose la resurse
}

isDisposed = true;
}

public void Dispose()
{
Dispose(true);
GC.SuppressFinalize(this);
}
}

Parca Finalize() si Dispose() sunt mai clare acuma.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP