350 kb jpg? in memory, that could be huge. perhaps even 20 or more mbs On Wednesday, April 18, 2012 3:29:46 AM UTC-7, ANKUR1486 wrote: > > Even i am loading 350 kb image its giving out of memory . > I have image in drawable folder > and setting the image in java code .:( > > > > On Tue, Apr 17, 2012 at 5:08 PM, Jim Graham <spooky1...@gmail.com> wrote: > >> The question about blending methods resolved itself when I switched to >> making the bitmaps for filters in the app. But one question still >> remains, and I need help with this one. >> >> When trying to blend the full-size camera image with an equal-size >> bitmap for the filter, unless I reduce the image size, I get an >> out of memory error. I really would like to allow users to get the >> maximum resolution possible. >> >> I start by converting the photo image from byte[] data to bitmap >> (for blending with the filter bitmap) and then immediately setting >> data to null. That doesn't seem to help at all. >> >> I have tried a combination of bmp.release(); and bmp = null;, which >> only results in a Force Close. It looks like this: >> >> // create full-sized filters instead of 640x480 >> Bitmap bmp1 = Bitmap.createScaledBitmap(src, width, height, false); >> // src.recycle() ; src = null; >> >> Bitmap bmp2 = Bitmap.createScaledBitmap(dest, width, height, false); >> // dest.recycle() ; dest = null; >> >> The intent being to release the memory used as quickly as possible >> in the method, rather than waiting until I finish completely with >> blending them. Unfortunately, if those are uncommented, the result >> is a Force Close. The Force Close gripes that I'm trying to use a bitmap >> that's already been recycled...but I don't use those bitmaps (src and >> dest) again. >> >> I also looked into the idea of splitting the task into chunks, but >> ultimately, there is still a huge amount of data ... right back >> where I started: out of memory error // Force Close. :-( >> >> Can anyone please let me how I can save these at full-size (that is, >> if there IS another way). If there isn't another way, I would at least >> appreciate that, then I can at least determine the maximum based on the >> device's available memory and reduce the image size before causing a >> force close. >> >> Thanks, >> --jim >> >> -- >> THE SCORE: ME: 2 CANCER: 0 >> 73 DE N5IAL (/4) MiSTie #49997 < Running FreeBSD 7.0 > >> spooky1...@gmail.com ICBM/Hurr.: 30.44406N 86.59909W >> >> "Now what *you* need is a proper pint of porter poured in a proper >> pewter porter pot.." --Peter Dalgaard in alt.sysadmin.recovery >> >> Android Apps Listing at http://www.jstrack.org/barcodes.html >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en > > >
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
