Question

I’ve create a c# application which uses up 150mb of memory (private bytes), mainly due to a big dictionary:

Dictionary<string, int> Txns = new Dictionary<string, int>();

I was wondering how to free this memory up. I’ve tried this:

Txns = null;
GC.Collect();

But it doesn’t seem to make much of a dent in my private bytes – they drop from say 155mb to 145mb.
Any clues?

Thanks

-edit-

Okay I’m having more luck with this code (it gets the private bytes down to 50mb), but why?

Txns.Clear(); // <- makes all the difference
Txns = null;
GC.Collect();

-edit-

Okay for everyone who says ‘don’t use GC.collect’, fair enough (I’m not going to debate that, other than saying you can see my C background coming through), but it doesn’t really answer my question:
Why does the garbage collector only free the memory if i clear the transaction list first? Shouldn’t it free the memory anyway, since the dictionary has been dereferenced?

Answer 1

Private bytes reflect the process’ memory usage. When objects are collected the associated memory segment may or may not be freed to the OS. The CLR manages memory at the OS level and since allocating and freeing memory isn’t free there’s no reason to free each piece of memory immediately as chances are that the application will probably request more memory later.