I am leaking memory on FrameLayout and Bitmap from this fragment below. Is is wise to have weak references on framelayout? I'd like to know how to perform it. The holder.image should I use weak references as well? I am using Universal-Image-Loader for loading large images.
One instance of "android.widget.FrameLayout" loaded by "<system class loader>" occupies 1,786,072 (13.27%) bytes. The memory is accumulated in one instance of "byte[]" loaded by "<system class loader>".
Keywords
android.widget.FrameLayout
byte[]
43 instances of "android.graphics.Bitmap", loaded by "<system class loader>" occupy 1,897,648 (14.10%) bytes.
Biggest instances:
•android.graphics.Bitmap @ 0x40e73900 - 1,048,656 (7.79%) bytes.
•android.graphics.Bitmap @ 0x40e79280 - 281,960 (2.09%) bytes.
Keywords
android.graphics.Bitmap
Fragment
@Override
public View getView(final int position, View convertView, ViewGroup parent) {
//final View view;
context = getActivity();
holder hold = new holder();
View view = (FrameLayout) getActivity().getLayoutInflater().inflate(R.layout.item_grid_image, parent, false);
//int imageWidth = loadedImage.getWidth();
//int imageHeight = loadedImage.getHeight();
if (convertView == null) {
//view = (LinearLayout) inflaterr.inflate(R.layout.item_grid_image, parent, false);
hold.image = (ImageView)view.findViewById(R.id.image);
} else {
view = (View) convertView;
hold.image = (ImageView)view.findViewById(R.id.image);
imageLoader.displayImage(values.get(position).get("imagePath").toString(),
hold.image, options, animateFirstListener );
}
class holder
{
ImageView image;
}