[
https://issues.apache.org/jira/browse/CB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498196#comment-13498196
]
john hight commented on CB-1404:
--------------------------------
I've tried putting a try/catch around the call to stopRecord, and it
doesn't hit. I've also tried putting a try/catch around a few spots in
iOSexec, and they don't either .... ALTHOUGH ... at one point I thought I
saw a "DOM exception", perhaps '11', appear as a value in the Safari
debugger as a property ("status" perhaps) of some variable in the sidebar.
Couldn't reproduce that behavior though, and it may have been something
that popped by putting one-too-many try/catch's or console.logs in iOSexec.
The secret to reproducing the error is to:
- click on Listen
- wait for a little more than 10 seconds and then click on Capture.
only have 10 seconds does the 2nd (of two) buffer/files start getting
recorded. You will see log messages for the 2nd buffer, buffer1,
like "*012-11-15
09:55:46.257 AudioRecall[28435:c07] [LOG] buffer1 listening .... 1.007 sec,
* ", when the 2nd buffer starts being recorded
If it still hits the alert "Returned from stopRecord" then we've failed in
getting you to reproduce the problem. If however, you do not get that
specific alert, and instead get a different one, like "buffer1 while listen
and default...." then you've reproduced the problem.
> 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
