Nevermind. Looks like loadUrl() is being loaded in the main thread. And setValue() is being called in the WebViewCoreThread.
On Jan 18, 2:12 pm, tatebn <[email protected]> wrote: > The javascript is actually generated in the getJSValue method. For > this test I'm using "2 + 2" as my expression. So I don't think the > actual js is the issue. > > How do I tell which thread which method call is happening in? > > On Jan 18, 1:20 pm, Streets Of Boston <[email protected]> wrote: > > > > > > > > > Very odd. > > > The call to loadUrl should just post a message with the Url on the > > WebViewCore which, in its turn, will run this url (javascript) on its own > > thread-pool. > > > I would examine your JavaScript as well. Maybe it does something that needs > > to be run on the same thread on which you call loadUrl (i.e. the main UI > > thread). > > > Remove the latches/semaphores temporarily and see on which thread your > > loadUrl is called an on which thread the setValue callback is called. If it > > is the same thread, that would explain the deadlock easily. If they are > > different threads, see if there is any other coordination/wait-states > > between these two threads that could cause the deadlock. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
