Out of Memory on really long lists about atarashii HOT 5 CLOSED

Everything I read claims that a ListView would appear to be the proper solution for this issue as it automatically recycles elements. However, Google talks about the grid list building block, which is basically what the application is trying to do.

It seems GridLists can recycle resources if handled correctly. It might be worthwhile to try to investigate the code discussed here as a possible solution to the memory issue and also as a chance to make the application feel more responsive.

from atarashii.

GridView actually does recycle its elements, the same way that ListView does, they both extend from AbsListView. I think the problem however is that the ImageDownloader class (which also handles saving and serving preloaded images) keeps an internal cache loaded in memory. Whole this helps performance after the images are initially out into the cache, the cache becomes too big and an OOM exception is thrown.

Ergo, the ImageDownloader needs to be made to release resources.

from atarashii.

That does make more sense than what I posted.

from atarashii.

The second link you posted is pretty good though, it reminded me that WeakReferences exist, which could probably fix the problem. (Another thing I never actually thought I'd use, how 'bout that!)

from atarashii.

Should be resolved as of 2a2c1fa, closing

from atarashii.