[jira] [Resolved] (CB-1403) camera.getPicture crashes moto Droid X with large images using DATA_URL

["Simon MacDonald (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon MacDonald resolved CB-1403.
---------------------------------

    Resolution: Won't Fix

Sadly there is nothing we can do about this one. When your Base64 encode an image that big the string data gets too big causing an out of memory exception in the JVM. OOM exceptions should never be caught since the JVM is in an unusable state once it is thrown so we are toast.
                
> camera.getPicture crashes moto Droid X with large images using DATA_URL
> -----------------------------------------------------------------------
>
>                 Key: CB-1403
>                 URL: https://issues.apache.org/jira/browse/CB-1403
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.7.0, 2.0.0
>         Environment: Moto Droid X, Android 2.3.4, Kernel 2.6.32.9-?
>            Reporter: Phil T.
>            Assignee: Joe Bowser
>
> When using navigator.camera.getPicture on Moto Droid X and the DATA_URL option, large return buffers will crash the app at the point of getPicture (generating a toast with force close).  Here's a sample of the code:
>     navigator.camera.getPicture(onPhotoDataSuccess, onFail,
>         { quality: 100,
>             destinationType: Camera.DestinationType.DATA_URL
>         }
>     );
> This code appears to function correctly on other devices we have tested that are running Android 2.3.4.  The issue is only seen on our Droid X devices (we have tried two different Droid X's).
> Reducing the image size by lowering the quality to 20 or below will allow the program to process correctly.  This can also be accomplished by shrinking the image size using the targetHeight/targetWidth options.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira