How to Go to main Activity

Question

I have wrote a code for a button to let me move from an activity in my application to my main activity. But an error occurred during run :

07-21 09:28:13.864: E/dalvikvm-heap(371): 25165824-byte external allocation too large for this process. 07-21 09:28:13.864: E/GraphicsJNI(371): VM won't let us allocate 25165824 bytes

I have used an image and stored them in my database but without any recycle is this the problem? Here is my code in bitmap :

try {
             Log.d("to get image", "ok");
            ImageView imageView = (ImageView) rowView.findViewById(R.id.imageView1);
          Bitmap bitmap = BitmapFactory.decodeStream((InputStream)new URL(imageInfo.get(position)).getContent());
          imageView.setImageBitmap(bitmap);
          } catch (MalformedURLException e) {
          e.printStackTrace();
         } catch (IOException e) {
        e.printStackTrace();
        }

My app suppose to retrieve default images from youtube for any key search word and store them in my data base.

My images are the default images for any youtube video so there is a large and small ones — Tolen, Jul 21 '13 at 09:54
just put this in your activity finish(); and it will take you back — mmoghrabi, Jul 21 '13 at 10:16

score 0 · Answer 1 · edited May 23 '17 at 10:25

0

This error means that You have a too large image inside. The problem here is, that You get a memory leak. If You use bitmaps, the best way is too use small bitmaps that fits on multiple devices. If You use bitmaps, also call recycle() if this bitmap is not used anymore. I recommend to read through this Guide to use Bitmaps:

http://developer.android.com/training/displaying-bitmaps/load-bitmap.html

Also, there is an alternative if recycling is not possible to You. You can scale Your bitmap to Your needs like perfectly explained in another thread here in stackoverflow:

Strange out of memory issue while loading an image to a Bitmap object

edited May 23 '17 at 10:25

Community

1
1

answered Jul 21 '13 at 09:54

Opiatefuchs

9,800
2
36
49

Unfortunately I would use the bitmap again. – Tolen Jul 21 '13 at 09:56
sure, but only if You start the main activity again, or? So at every start, create this bitmap again, at every finish, recycle this image. – Opiatefuchs Jul 21 '13 at 10:03
Opiatefuchs: thank you a lot I missed that, and will try it thanks. – Tolen Jul 21 '13 at 10:19
I hope you will get success, if not come back to here – Opiatefuchs Jul 21 '13 at 10:30
Opiatefuchs: I have a confusion from what the recycle functionality is. I understood that it garbages the image after using it am I wrong? – Tolen Jul 21 '13 at 11:21
by calling recycle it GCs the bitmap, You are wright. If this is not an options see my edit. – Opiatefuchs Jul 21 '13 at 12:16
Opiatefuchs : I am sorry but I am new here , I know it sounds like silly question but where is your edit?. – Tolen Jul 21 '13 at 12:26
sorry haven´t marked it as edit :), it´s just below the first link – Opiatefuchs Jul 21 '13 at 12:59
Oiatefuchs: Never mind. :) thanks a lot. it helped me . God bless you – Tolen Jul 22 '13 at 08:45

talkol · Answer 2 · 2013-07-21T10:33:27.940

Android apps have a limited heap size (minimum on old devices is as little as 16MB). This varies per device, so be careful during QA. Since a bitmap can take as much as 4 bytes per pixel, large bitmaps can easily fill up your heap (1000 x 1000 pixels = 3.8MB). Your bitmap seems to take 25MB which is huge!

What this means is that you have to be very careful and use several tactics to avoid wasting memory:

When you don't need the bitmap anymore, release it and call bitmap.recycle() to make sure the memory is freed immediately. If you need the bitmap again in the future, you can load it again from disk/resources.
If the bitmap is larger than your screen size, you can scale it down to save memory. The technique here will let you load it initially reduced by 2/3/4.. If you need more fine-tuning, you can load it full size and then rescale using Bitmap.createScaledBitmap. Just don't forget to recycle() the original large bitmap immediately.

Please note that with bitmap scaling, I did not recommend to just resize your source images. Different Android devices have different resolutions. So I would keep my source images big enough to look perfect on the highest resolution devices available. Low resolution devices usually have less heap memory, so the runtime scaling takes care of those.

talkol: that would be a pleasure :) – Tolen Jul 21 '13 at 11:24 — Tolen, Jul 21 '13 at 11:24

How to Go to main Activity

2 Answers2