Comments on: GWT Image.prefetch memory leak and suggestions for improvement http://pathfindersoftware.com/2008/01/gwt-imageprefet/ The Fastest Way to Launch Successful Software Thu, 19 Jan 2012 16:36:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: joe http://pathfindersoftware.com/2008/01/gwt-imageprefet/#comment-7612 joe Tue, 28 Sep 2010 16:04:38 +0000 http://www.pathf.com/blogs/?p=104#comment-7612 Maybe the solution is to use an LRU (least-recently-used) cache. It discards the least recently used items first. This could be implemented in your own gwt class, without being dependent on the Image class. For example: Map mImagePrefetchCache = new LinkedHashMap( MAX_ENTRIES, .75F, true ) { protected boolean removeEldestEntry( Map.Entry eldest ) { return size() > MAX_ENTRIES; } }; Maybe the solution is to use an LRU (least-recently-used) cache. It discards the least recently used items first. This could be implemented in your own gwt class, without being dependent on the Image class.

For example:

Map mImagePrefetchCache = new LinkedHashMap( MAX_ENTRIES, .75F, true )
{
protected boolean removeEldestEntry( Map.Entry eldest )
{
return size() > MAX_ENTRIES;
}
};

]]> By: Harold Campbell http://pathfindersoftware.com/2008/01/gwt-imageprefet/#comment-7611 Harold Campbell Sun, 24 Aug 2008 03:26:23 +0000 http://www.pathf.com/blogs/?p=104#comment-7611 Good point. I had noticed the same thing. I still don't like the fact that I must explicitly call the release. I think the framework should be smart enough to GC the images in the prefetchImages HashMap Good point. I had noticed the same thing. I still don’t like the fact that I must explicitly call the release. I think the framework should be smart enough to GC the images in the prefetchImages HashMap

]]>