Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Fri, 16 Nov 2012 17:52:12 +0000 (UTC)
From: "john hight (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <711142979.124858.1353088332464.JavaMail.jiratomcat@arcas>
In-Reply-To: <647820802.54913.1347158887501.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CB-1404) EXC_BAD_ACCESS when using
 XHR_WITH_PAYLOAD bridge mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

john hight commented on CB-1404:
--------------------------------

Some details to help understand what the app is doing:

   - When LISTENing, the app is recording two files. Each file records for
   20 seconds, stops (with stopRecord), and then starts recording again.
    Additionally, one of the two files (buffer1) does not start off its
   sequence until the 10 second mark.  The app is meant to have each file stop
   and restart approximately halfway through the recording of the other buffer.
   - In the scenario for reproducing the bug,  you start the listening
   sequence by clicking LISTEN.  buffer0 starts recording, and 10 seconds
   later, buffer1 starts recording.
   - Clicking CAPTURE after the 10 second mark essentially stops the
   recording of buffer1 and continues to let buffer0 record (for a much longer
   period of time), and causes the LISTEN file/buffer cycling to stop.
   - It's this call to stopRecord for buffer1 after the 10 sec mark that
   reproduces the problem.
   - The alert() placed after the call to stopRecord is only there
   temporarily to help try and diagnose the problem If that alert is not the
   first alert hit after clicking CAPTURE after 10 seconds, then the bug has
   been reproduced (and forget about what any other alert may proclaim).

John


> 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