Skip to content Skip to sidebar Skip to footer

Out Of Memory On A Byte Allocation (Bitmap As String To Webservice Using Soap)

Am having a bitmap , so I want to upload a webserivceas string and want to retrive the string. For converting bitmap to string am using: ByteArrayOutputStream stream = new ByteArr

Solution 1:

You are creating 3 copies of an 11MB image(bitmap, stream, strBase64). So reduce the memory usage by calling

bitmap.recycle();

below this line:

bitmap.compress(Bitmap.CompressFormat.PNG, 100, stream);

Also close the stream when you are done with it(below stream.toByteArray();):

stream.close();
stream = null;

Remember that there is no guarantee that memory will be cleaned immediately after these calls. Proper way to handle this type of situation is to transfer large files chunk by chunk.


Solution 2:

An 11 Million byte allocation much larger than most phones' heap can handle. you definitely don't want to be holding a byte array of that size in memory.

Try using insample size with

BitmapFactory.decodeStream(InputStream is, Rect outPadding, BitmapFactory.Options opts)

and settings options to use insample size to return a reasonably sized image.


Solution 3:

A simple fix for some might be to add android:configChanges="orientation|screenSize" to your manifest. In my case, the Nexus_S emulator was crashing without this line, while the actual Nexus 7 device I was testing on wasn't crashing on rotation.

Adding this appears to be an easy fix for apps that have a couple large "match_parent" bitmaps to rotate and resize.

Careful if you are building for APIs before 13!


Post a Comment for "Out Of Memory On A Byte Allocation (Bitmap As String To Webservice Using Soap)"