[
https://issues.apache.org/jira/browse/CB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498395#comment-13498395
]
john hight commented on CB-1404:
--------------------------------
I believe you've replicated the bug since the first alert you get is not
the stopRecord alert. The stopRecord alert you subsequently see is
"probably" the return from the second of two stopRecords that get issued
(one for each file), but it could be misleading to even guess at that since
anything after the first "problem" (the last of stopRecord alert first)
could be hard to predict.
> 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
