Releasing memory immediately

[Michael]

Hello all,

Does anybody knows how to destroy (in C#) a non disposable object (an object that has not implemented a dispose method) so the memory used by it could be released immediately?

I tried setting the object value to null, but it doesn't worked!

I really appreciate any help.


Thank you all

[Hack]

What code are you using that isn't working?

Are you getting an error? If so, what?

[Michael]

Hello Hack,

I have to destroy a Dictionary object (System.Collections.Generic.Dictionary<TKey, TValue>) than contains the Key and as the value, it contains an object.

The thing is that even if I put null as the value of the object, I can't see the memory used to be released.

Unfortunately this code is repeated for every record in a datareader, so as the memory is never released, it continues to raise until we get an our of memory error.

the code is something like this:

dDataDictionary = new Dictionary<ID, myObject>

What I tried to do to release the memory was:

dDataDictionary = null;

but it doesnt worked....

Any ideas?

[Hack]

Try disposing of it

dDataDictionary.Dispose

[Michael]

Hi Hack,

Unfortunately (and amazingly) dDataDictionary doesn't contains a "Dispose" method!!!.

The available options are:

Add
Aggregate<>
All<>
Any<>
AsEnumerable<>
AsQueryable
AsQueryable<>
Average<>
Cast<>
Clear
Comparer
Concat<>
Contains<>
ContainsKey
ContainsValue
Count
Count<>
DefaultIfEmpty<>
Distinct<>
ElementAt<>
ElementAtOrDefault<>
Equals
Except<>
First<>
FirstOrDefault<>
GetEnumerator
GetHashCode
GetObjectData
GetType
GroupBy<>
GroupJoin<>
Intersect<>
Join<>
Keys
Last<>
LastOrDefault<>
LongCount<>
Max<>
Min<>
OfType<>
OnDeserialization
OrderBy<>
OrderByDescending<>
Remove
Reverse<>
Select<>
SelectMany<>
SequenceEqual<>
Single<>
SingleOrDefault<>
Skip<>
SkipWhile<>
Sum<>
Take<>
TakeWhile<>
ToArray<>
ToDictionary<>
ToList<>
ToLookup<>
ToString
TryGetValue
Union<>
Values
Where<>


That's all...

[Michael]

Hello guys,

I could release the memory, but I think it's not the better way I could do it, so i would REALLY appreciate your help.

What I did is setting a null value to each object of the Dictionary object with an specific key, something like this:

dDataDictionary[kKey].Object1 = null;
dDataDictionary[kKey].Object2 = null;
dDataDictionary[kKey].Object3 = null;

The thing is, after assigning the null values to all the objects within dDataDictionary, I anyway have to "force" the memory to be released, and I did it using:

GC.Collect();

This way I can restore the memory to the same levels it was before starting the process that consume the resources (let's say it started with 60Mb, it raided to 180Mb, and afer GC.Collect(), it went back again to 60Mb).

If I doesn'tuse GC.Collect(), the memory is never released even if I assigned the null value.

I know it's risky to force GC to do it's job, so I would like to know if anyone has a better solution for this?

Thank you all.