incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-391) crashing on iOS after memory warning
Date Tue, 03 Apr 2012 00:55:23 GMT


Shazron Abdullah commented on CB-391:

Following your steps, found the crash:
(self.pickerController is nil at this point)

self.pickerController is nil at this point because CDVCamera's dealloc method was called.
CDVCamera's dealloc method was called because all the objects in CDVViewController's pluginObjects
property (a NSArray) are being purged because of the [super didReceiveMemoryWarning] call.
Mystery solved, fix still unknown...
> crashing on iOS after memory warning
> ------------------------------------------------------------------
>                 Key: CB-391
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.5.0
>         Environment: 2 x iPhone 4S, iOS 5.1. Can't replicate on simulator or iHone 3GS
with iOS 5.0.1
>            Reporter: Richard Kimber
>            Assignee: Shazron Abdullah
>         Attachments: Wulvern_2012-03-27-141033_Richs-iPhone.crash
> getPicture has become very unstable on previously working code, affecting both Phonegap
1.4.1 and Cordova 1.5.0. Contributing factors, since last working build I have upgraded Xcode
to 4.3.2 (from whatever the last version was) and iPhone to iOS 5.1 from 5.0.1.
> Memory warning is received on displaying camera, app crashes when you select 'use'. Restarting
device usually resolves problem for a limited amount of time. Problem is intermittent and
sometime difficult to replicate. Selecting from Photo library works fine.
> Options used:
> 		var options = {
> 			quality: 40,
> 			sourceType: Camera.DestinationType.FILE_URI
> 		};
> See!topic/phonegap/ZLbw0s4JREs
for more details.
> See attached for example crash log.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message