cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <>
Subject [jira] [Commented] (CB-1404) EXC_BAD_ACCESS when using XHR_WITH_PAYLOAD bridge mode
Date Wed, 14 Nov 2012 19:02:12 GMT


Andrew Grieve commented on CB-1404:

Hmm, yeah, not sure what's going on. If it's reproducible, might be worth putting a try/catch
in there to see if a JS exception is happening.

Of note:
-XHR_WITH_PAYLOAD is not used in 2.2 by default. It's always NO_PAYLOAD.
-This CL makes it even less likely to attempt an XHR when there is already one in progress:;a=blobdiff;f=lib/ios/exec.js;h=7ce52d94da0e834104e0ee5cc1ceb70e8cbe8104;hp=c6b8edd7f9518c0a1ca726db2216f64a45a0e0a7;hb=86411246aba4292734b9bb46dc9128e28391e424;hpb=c3517e7703ab9a1335db8a3d0974b045ae3107e5
> EXC_BAD_ACCESS when using XHR_WITH_PAYLOAD bridge mode 
> -------------------------------------------------------
>                 Key: CB-1404
>                 URL:
>             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:

View raw message