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

Richard B Knoll commented on CB-9755:
-------------------------------------

Is this still an issue? If so, [~gabereiser] would you mind positing some code 
for reproducing the problem (such as the camera options you are using)?

> Plugin Camera getPhoto crashes on iOS for iPad Mini 1st gen.
> ------------------------------------------------------------
>
>                 Key: CB-9755
>                 URL: https://issues.apache.org/jira/browse/CB-9755
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS, Plugin Camera
>    Affects Versions: 3.5.0
>         Environment: iOS 9, iPad Mini 1st Gen, Cordova, cordova-plugin-camera
>            Reporter: Gabriel Reiser
>              Labels: ios
>
> Ever since iOS 9 was released we have had this bug when calling 
> `navigator.camera.getPhoto` the underlying iOS code called 
> CDVCamera.takePhoto is called, however, upon taking a photo, returning it, 
> opening a keyboard tray from a text field, and trying to capture a photo 
> again, our app was crashing with a 0x0BBADBEEF ACCESS VIOLATION.
> I tested out removing the code that makes it run in a background thread and 
> it seemed to fixed the issue.  Seems this issue was introduced back in April 
> from the commit logs.  Replacing calls from self to weakSelf and running 
> things in background threads without fully testing that they don't thread 
> lock and cause access violations.
> We have an internal fork for this fix which has plagued us since iOS 9's 
> release where we remove the code that makes it run in a background context 
> but I'm curious as to what changed in iOS 9 to make it crash like this on 
> iPad Mini.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to