After make a session.close() I still have all session resources in memory. How can I assure that I release all the resources?

Thank you.

Some of the code:

ISession session = GISAUtils.SessionFactory.OpenSession();
ITransaction tx = session.BeginTransaction();

initNivel(session, id);
long frdbId = initFRDBase(session, id);
initRelacaoHierarquica(session, id);

if (frdbId != -1)
{
initSFRDContexto(session, frdbId);
initTipoTradicaoDocumental(session, frdbId);
initSFRDDatasProducao(session, frdbId);
}

tx.Commit();
session.Flush();
session.Close();

Test code:

[Test]
public void GetAllNivelDocumental()
{
IList<long> ids = GISAUtils.getAllNivelDocumentalIds();

int i = 0;
long initMemory = GC.GetTotalMemory(true);
foreach (long id in ids)
{
NivelDocumental doc = new NivelDocumental(id);
Assert.IsNotNull(doc);
}
long usedMemory = (GC.GetTotalMemory(true) - initMemory) / 1024;

Console.WriteLine("All Documents Memory: " + usedMemory.ToString() + "KB");

}

This gives me +/- 450MB allocated.

session.Dispose();

You could alternatively put your session in a using block.

Thank you for answer, I have tried all the simple tricks (I think), dispose(), flush() evict of every single object created, but nothing seems to work.

Hrm, if you've got access to the sessionFactory that generated the session, you can call something like:



This should unbind the current session, which may be what you need here.

Thank you, but it doesn't work. The memory continues to grow forever... :(

The only thing that seams to work is to transform the sessionFactory in an instance variable and close the sessionFactory every time I close the session. But this causes a big overhead... :(

Does someone have any more ideas?
Thanks in advance!

What exactly do you mean by still having everything in memory? If you mean that you have removed all references to the object but it is still taking up memory, then that is by design, since the .NET garbage collector does not run immediately after you remove all references to an object. If you mean that you can still access the object, then you're still holding a reference to it, which is why the GC isn't releasing the memory for it.

To clarify, using Session.Close() or Session.Dispose() releases all unmanaged resources. After that, it's up to the GC to decide when it's best to clean up managed memory. If you absolutely need to get rid of the object from memory, you can call GC.Collect() for force garbage collection, although this is rarely recommended.

Tank you Robert! I'm doing the collection from GC in the unit tests and even that doesn't remove the resources from the memory.

Sorry, I missed the GC.GetTotalMemory(true) in your tests. In that case, I'd guess that maybe the Session object is caught in the finalization queue for the first collection. Try adding Session.Dispose() to the end of your code, or change the line into a Using block.

@RobertD:
noube already tried that, see http://forum.hibernate.org/viewtopic.ph ... 41#2394941

@noube:
You could try posting at the google group: http://groups.google.com.ar/group/nhusers
The developers are much more active there.