You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2012/09/25 19:20:09 UTC

[jira] [Resolved] (CB-1404) EXC_BAD_ACCESS when using XHR_WITH_PAYLOAD bridge mode

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

Andrew Grieve resolved CB-1404.
-------------------------------

    Resolution: Fixed

Tom, I like your reasoning. I didn't bother with trying your test case, but instead applied your patch:

https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-js.git;a=commit;h=533c707ee48f1191fde2d92376b1a5cc45e4a72a

I've also changed the default bridge mode back to XHR_OPTIONAL_PAYLOAD.

We can re-open if the crash shows up again.
                
> EXC_BAD_ACCESS when using XHR_WITH_PAYLOAD bridge mode 
> -------------------------------------------------------
>
>                 Key: CB-1404
>                 URL: https://issues.apache.org/jira/browse/CB-1404
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.1.0
>         Environment: iPad 2, iOS 5.1.1
>            Reporter: Tom Clarkson
>            Assignee: Andrew Grieve
>             Fix For: 2.2.0
>
>
> When calling a plugin the app crashes on WebThread with EXC_BAD_ACCESS in WebCore::DocumentThreadableLoader::cancel.
> This appears to be some sort of timing issue, as it does not happen on every call - I am seeing it in an autosave function which makes lots of calls to PGSQLitePlugin. 
> The error did not appear before upgrading to 2.1, and setting the bridge mode to IFRAME_NAV restores the previous behaviour (no crashes, but odd scrolling functionality).
> Setting the bridge mode to XHR_NO_PAYLOAD also seems to fix it - not sure if removing the payload actually does anything different or just makes it fast enough that the timing condition does not come up in normal app usage.
>   

--
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