incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-885) Crash when sliding the notification tray and/or tel link confirm dialog
Date Fri, 08 Jun 2012 22:31:23 GMT


Shazron Abdullah commented on CB-885:

I think I know what's going on. When you do either of those actions, the app is not active
anymore, and usually this signals that you are going into the background, and we do a backup
of your localStorage database. 

Recently there was a change that made this backup async, (previously it was synchronous),
and thus we have a threading issue – UIKit was only designed to be used on the main thread.
The change was this:
> Crash when sliding the notification tray and/or tel link confirm dialog
> -----------------------------------------------------------------------
>                 Key: CB-885
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.8.0
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>            Priority: Critical
> my app crashes when I invoke some native iOS UI (i.e. Manually pulling the Notification
tray on top of the app, clicking a link that invokes a native Call dialog, etc). 
> EmployeeDirectory18[2451:7103] bool _WebTryThreadLock(bool), 0x3a2f60: Tried to obtain
the web lock from a thread other than the main thread or the web thread. This may be a result
of calling to UIKit from a secondary thread. Crashing now...
> 1   _ZL17_WebTryThreadLockb
> 2   WebThreadLock
> 3   -[UIWebView stringByEvaluatingJavaScriptFromString:]
> 4   -[CDVPlugin writeJavascript:]
> 5   -[CDVLocalStorage backup:withDict:]
> 6   __33-[CDVLocalStorage onResignActive]_block_invoke_0201
> 7   _dispatch_call_block_and_release
> 8   _dispatch_worker_thread2
> 9   _pthread_wqthread
> 10  start_wqthread
> (lldb) 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message