HashTable problem

[EFileTahi-A]

How the Foxtrot can I release the Hashtable's associated resources?

I load 30 large bmps which will "eat" about 45MB of ram. Then, If I reload them, an aditional 45MB will be consumed. So, basicaly, If I reload these pictures 5 times more the 200MB will be consumed, even with the myHasTable.Clear() property and the CollectGarbage before reloading these images...

Also, the Hashtable don't have the "Dispose()" property... What the...

This Hastable of mine is static so I would only like to dispose it's associated resources rather then disposing the object itself...

 

[PlausiblyDamp]

You will need to dispose of the bitmaps in the hashtable, not the hashtable itself.

 

[EFileTahi-A]

Ok, but how will I do that? I'm loading the images from file directly to the hash table:

myHashTable.Add(sKeyImageName, Image.FromFile(sPath));

 

[EFileTahi-A]

Ok, nevermind... I made it

Thank you PlausiblyDamp for the tip.

- THREAD CLOSED -

 

[PlausiblyDamp]

something like

System.Collections.Hashtable h = new Hashtable();

//add stuff in
h.Add("test", new Bitmap(1000,1000));

//to dispose
foreach (object o in h.Values)
	{
	IDisposable d = o as IDisposable;
	if (d != null)
		d.Dispose();
	}

should do it

 

[EFileTahi-A]

Hmmm... interesting.

I used another method though. But yours sounds more professional and definately less resourse consuming then mine.

 

[Joe Mamma]

isnt this what an image list is for? Wont disposing an image list dispose the Bitmaps?

load your images into an image list.
Add references to the images to a hash table.
to free, dispose the image list, reset your hashtable.

 

[EFileTahi-A]

Hi Joe,

Unfortunately the Image List object is limited to 256 by 256 pixels.

 

[Joe Mamma]

Hi Joe,

Unfortunately the Image List object is limited to 256 by 256 pixels.

yeah. . . that could be a problem I guess

 

[Joe Mamma]

yeah. . . that could be a problem I guess

by the way. . . are you in 1.1 or 2.0?

 

[Joe Mamma]

I can add a 1024x768 to an imagelist in 2.0.

is this a limitation to 1.1?

 

[Joe Mamma]

I can add a 1024x768 to an imagelist in 2.0.

is this a limitation to 1.1?

I can do it in 1.1 too.

 

[Joe Mamma]

I can do it in 1.1 too.

ahh. . . Im a moron. . yeah I can add it. . . but it comes back out as the size specified by the Imagelist.

that sux.

 

[EFileTahi-A]

LOL! Now you confused me! You mean they resized in both 1.1 and 2.0?

I'm using 1.1 by the way.

 

[Cags]

I believe what Joe Mamma meant was that you can add an image of any size to an image list, but it automatically resizes the Image to the size specified by the Image list (which is a maximum of 256).

 

[EFileTahi-A]

I believe what Joe Mamma meant was that you can add an image of any size to an image list, but it automatically resizes the Image to the size specified by the Image list (which is a maximum of 256).

Yeah I understood that. What I did not realise was if that "resize thingie" also happens in v2.0