c# object caching and reference counting

[colin]

Hi,
I need to cache various resource objects such as images for example,
wich might be referenced from multiple objects
(wich could be considered documents for ease of discusion)
and the idea is simply to make sure they arnt duplicated
as they take up considerable memory, so I can look up
to see if an existing copy exists.

however once they are in the cache how can I ensure they get released,
when they are no longer referenced, as now my cache list is referencing
them,
so the GC wont free them.

can I look at the underlying reference count and so release it from my cache
if the count is 1?
I cant seem to find how to do this, at least not inside c#.

I realy dont want to have to keep a track of seperate reference count as
this
is something I hoped id got away from with managed code.

or is there a way to find all existing objects of a certain class?

a couple of alternatives would be

1) to hold a wrapper wich releases the bitmap when it hasnt been used for
ages,
but can reload it when required from the source,
however this needs a reference to the source wich means that the source no
longer gets released
when its dereferenced.

2) to have a root item wich all source documents are referenced from and to
periodically
keep the cache up to date with this. this is probably much like the GC
operation.
however this is probably quite complicated and not all the source types are
under my control.

I thought I heard someone talk about such a cache, however when I tried to
look
there are so many other types of cache, relating to .net assemblies etc.

the images are actually textures for my 3d objects,
but theres other types too wich are large enought o try and avoid
duplicating.

many thanks
Colin =^.^=

[Terry Rogers]

On May 22, 12:06 pm, "colin" <colin.ro...@nt world.NOSPAM.co mwrote:

Hi,
I need to cache various resource objects such as images for example,
wich might be referenced from multiple objects
(wich could be considered documents for ease of discusion)
and the idea is simply to make sure they arnt duplicated
as they take up considerable memory, so I can look up
to see if an existing copy exists.

however once they are in the cache how can I ensure they get released,
when they are no longer referenced, as now my cache list is referencing
them,
so the GC wont free them.

can I look at the underlying reference count and so release it from my cache
if the count is 1?
I cant seem to find how to do this, at least not inside c#.

I realy dont want to have to keep a track of seperate reference count as
this
is something I hoped id got away from with managed code.

or is there a way to find all existing objects of a certain class?

a couple of alternatives would be

1) to hold a wrapper wich releases the bitmap when it hasnt been used for
ages,
but can reload it when required from the source,
however this needs a reference to the source wich means that the source no
longer gets released
when its dereferenced.

2) to have a root item wich all source documents are referenced from and to
periodically
keep the cache up to date with this. this is probably much like the GC
operation.
however this is probably quite complicated and not all the source types are
under my control.

I thought I heard someone talk about such a cache, however when I tried to
look
there are so many other types of cache, relating to .net assemblies etc.

the images are actually textures for my 3d objects,
but theres other types too wich are large enought o try and avoid
duplicating.

many thanks
Colin =^.^=

You could use a WeakReference to store items in the cache, that way
the images can still be garbage collected as normal.

For example:

public class ImageCache
{
private IDictionary<str ing,WeakReferen ce_cache = new
Dictionary<stri ng, WeakReference>( );
public Image GetImage(string path)
{
WeakReference reference;
if(_cache.TryGe tValue(path, out reference))
{
if(reference.Is Alive)
{
return (Image) reference.Targe t;
}
else
{
// image has been garbage collected
// remove reference from cache
_cache.Remove(p ath);
}
}

// not in cache, so load
Image image = Image.FromFile( path);
reference = new WeakReference(i mage);
_cache.Add(path , reference);
return image;
}
}

[Marc Gravell]

Perhaps you could try using a WeakReference in the list; you will need
to cast it to image to extract it, but a WeakReference won't prevent GC
- if everything else has let go of the image, then it will be collected,
and the WeakReference will report this when you look at it.

Marc

[colin]

aha thats super thanks and to mark too :)
Colin =^.^=

"Terry Rogers" <ro**********@g mail.comwrote in message
news:33******** *************** ***********@c58 g2000hsc.google groups.com...

On May 22, 12:06 pm, "colin" <colin.ro...@nt world.NOSPAM.co mwrote:

>Hi,
I need to cache various resource objects such as images for example,

......

>Colin =^.^=

You could use a WeakReference to store items in the cache, that way
the images can still be garbage collected as normal.

For example:

public class ImageCache
{
private IDictionary<str ing,WeakReferen ce_cache = new
Dictionary<stri ng, WeakReference>( );
public Image GetImage(string path)
{
WeakReference reference;
if(_cache.TryGe tValue(path, out reference))
{
if(reference.Is Alive)
{
return (Image) reference.Targe t;
}
else
{
// image has been garbage collected
// remove reference from cache
_cache.Remove(p ath);
}
}

// not in cache, so load
Image image = Image.FromFile( path);
reference = new WeakReference(i mage);
_cache.Add(path , reference);
return image;
}
}

[parez]

colin wrote:

Hi,
I need to cache various resource objects such as images for example,
wich might be referenced from multiple objects
(wich could be considered documents for ease of discusion)
and the idea is simply to make sure they arnt duplicated
as they take up considerable memory, so I can look up
to see if an existing copy exists.

however once they are in the cache how can I ensure they get released,
when they are no longer referenced, as now my cache list is referencing
them,
so the GC wont free them.

can I look at the underlying reference count and so release it from my cache
if the count is 1?
I cant seem to find how to do this, at least not inside c#.

I realy dont want to have to keep a track of seperate reference count as
this
is something I hoped id got away from with managed code.

or is there a way to find all existing objects of a certain class?

a couple of alternatives would be

1) to hold a wrapper wich releases the bitmap when it hasnt been used for
ages,
but can reload it when required from the source,
however this needs a reference to the source wich means that the source no
longer gets released
when its dereferenced.

2) to have a root item wich all source documents are referenced from and to
periodically
keep the cache up to date with this. this is probably much like the GC
operation.
however this is probably quite complicated and not all the source types are
under my control.

I thought I heard someone talk about such a cache, however when I tried to
look
there are so many other types of cache, relating to .net assemblies etc.

the images are actually textures for my 3d objects,
but theres other types too wich are large enought o try and avoid
duplicating.

many thanks
Colin =^.^=

I wish i had known about this WeakReference class two years ago. I had
implemented a similar class for expirable objects that checked the
"time inserted" before returning the object or null.
Also used a timer to remove the objects from the hashtable based on
inserted time.

[Peter Duniho]

On Thu, 22 May 2008 04:47:33 -0700, Marc Gravell <ma**********@g mail.com>
wrote:

Perhaps you could try using a WeakReference in the list; you will need
to cast it to image to extract it, but a WeakReference won't prevent GC
- if everything else has let go of the image, then it will be collected,
and the WeakReference will report this when you look at it.

The one thing I'd be worried about is using WeakReference with classes
that implement IDisposable (e.g. Bitmap). I realize that knowing that the
instance has in fact been garbage-collected goes a long way toward
alleviating that concern, but it seems like you could still theoretically
have unmanaged resources being left unreleased for some time.

Any thoughts on that?

Pete