Return-Path: 
 <callback-dev-return-3262-apmail-incubator-callback-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 45CBD9B5C
	for <apmail-incubator-callback-dev-archive@minotaur.apache.org>;
 Wed, 14 Mar 2012 15:01:05 +0000 (UTC)
Received: (qmail 45062 invoked by uid 500); 14 Mar 2012 15:01:04 -0000
Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org
Received: (qmail 45034 invoked by uid 500); 14 Mar 2012 15:01:04 -0000
Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:callback-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:callback-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:callback-dev@incubator.apache.org>
List-Id: <callback-dev.incubator.apache.org>
Reply-To: callback-dev@incubator.apache.org
Delivered-To: mailing list callback-dev@incubator.apache.org
Received: (qmail 44976 invoked by uid 99); 14 Mar 2012 15:01:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 15:01:04 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Mar 2012 15:01:02 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 33E511FE15
	for <callback-dev@incubator.apache.org>;
 Wed, 14 Mar 2012 15:00:40 +0000 (UTC)
Date: Wed, 14 Mar 2012 15:00:40 +0000 (UTC)
From: "sandstrom (Commented) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <794854217.13012.1331737240250.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1028604789.2251.1329740854703.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CB-264) camera.getPicture() CRASH when
 repeatedly called on iOS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/CB-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229242#comment-13229242 ] 

sandstrom commented on CB-264:
------------------------------

Looks like I might have tracked down the error (though I must test some more to be sure). If my early results hold, the error was caused by triggering `navigator.camera.getPicture` from a <button> element instead of an <a> element, probably coupled with inclusion of emberjs, handlebars or jquery. Sounds so weird that I hardly believe it myself, but just swapping the element type seem to work.

I've tried to isolate the error but haven't managed, so I guess it's some combination of the above that causes the problem.
                
> camera.getPicture() CRASH when repeatedly called on iOS
> -------------------------------------------------------
>
>                 Key: CB-264
>                 URL: https://issues.apache.org/jira/browse/CB-264
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.4.0
>         Environment: PG 1.4.1 on iOS
> Crash on iPhone4S, iPad2 and iPod Touch
>            Reporter: Phil Haeusler
>            Assignee: Shazron Abdullah
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> We are experiencing an intermittent crash when calling camera.getPicture() on multiple devices.  The crash can occur either as the pickerController is popped in from the bottom, or after you tap the Use button to accept the picture.  The app requires the taking and review of pictures in a fairly fast manner.  We've found the crash can occur anytime after we've capture only 1 or 2 photos.  Sometimes we go for quite a while without crashing.
> We see that the images captured are stored in tmp/photo_nnn.jpg, but we do not believe we've reached any storage limits here.  
> We are taking the image and displaying it in a <img> - so possibly there is an issue with UIWebView retaining references to previously loaded images, and exhausting it's memory.  But not really sure if that could be an issue.
> We've created a small app that we can crash by repeated taking and viewing images.  There doesn't seem to be anything special about it.
> https://gist.github.com/1868997

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira