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

2012-11-17 Thread john hight (JIRA)

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

john hight commented on CB-1404:


Problem solved.  I had my blinders on regarding the order that callbacks
come in sometimes.

Thanks for setting my straight





 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


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

2012-11-16 Thread john hight (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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


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

2012-11-15 Thread john hight (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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


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

2012-11-14 Thread john hight (JIRA)

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

john hight commented on CB-1404:


I'd be glad to ... except that due to some un-thriftiness on my part,
I've got a lot of images ballooning the size up to about 64MB.  I'll see if
I can get the size ratcheted down.  Unless, of course, you're ok with
getting it off of github:
https://github.com/johnhight/AudioRecall.git(I'll have it public for a
bit)





 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


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

2012-11-14 Thread john hight (JIRA)

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

john hight commented on CB-1404:


Oops, nevermind, I'm a newbie to JIRA, didn't know I could attach-upload a
file on the site. I'll upload.





 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


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

2012-11-14 Thread john hight (JIRA)

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

john hight commented on CB-1404:


Too large to upload as well, it will be on github til I figure out how to make 
it smaller.

 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