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

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…