Note that just because heap limits aren't imposed on the native heap like
they are on the Java heap doesn't mean that there aren't limits. The
failure cases are just more difficult -- not allowing stuff to work in the
background when it should to your application just silently being killed.
You *
I'm working on a simple image manipulation app that requires opening
bitmaps at full resolution, which of course results in OutOfMemory
issues. I know that the short answer is to simply use less memory via
BitmapFactory's inSampleSize Option to downsample the bitmap, but for
this app I really would
Java doesnt support pointers or direct access to memory which is why native
routines exist...why dont you open the files as streams and only render what
is require for the view orrescale the image?
Regards,Sy
On 8 Jun 2011 18:21, "Erik R" wrote:
I'm working on a simple image manipulation ap
There is no such plan at the moment.
On Wed, Jun 8, 2011 at 10:17 AM, Erik R wrote:
> I'm working on a simple image manipulation app that requires opening
> bitmaps at full resolution, which of course results in OutOfMemory
> issues. I know that the short answer is to simply use less memory via
>
4 matches
Mail list logo
