Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6AC931010C for ; Mon, 24 Feb 2014 19:23:38 +0000 (UTC) Received: (qmail 68415 invoked by uid 500); 24 Feb 2014 19:23:37 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 68376 invoked by uid 500); 24 Feb 2014 19:23:37 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 68368 invoked by uid 99); 24 Feb 2014 19:23:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 19:23:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 19:23:33 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so1592236pbb.8 for ; Mon, 24 Feb 2014 11:23:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=DD6uS0hDkfA4TK+83R6IWl85YNggRmbgZKLU4HFavXw=; b=MxiuvAhVmqogW8sx1h1d6WyBx+ePx/wqM0UDyCH5aZGiGmjcRVuxXUpAehZxjL2KEv g989iP5Y91tmTVLH+g7X+T0l+ix9i6oTa/bdOdPKdci0uGvEBxD1k/NE8ZRvyZofTPjv O8bFGuPiyJrAU0WAOOu3hpL3hjRYMAtW0iBKoi2SkyMe5t4AH6Fe0pouk+1eRcKhUURp 3C6psNgkw6ZrMDUtovx5R8OObajIEwIt3FU1M3/CuLQg4PHDcskEecrM5697IjiQSLU6 2CpqTg8zCSlAicUbYsm8jtj0x/Xm0VWS271v2X85DmRsbLTlNEIAZ0VX+s71gM7n51V6 Zy+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=DD6uS0hDkfA4TK+83R6IWl85YNggRmbgZKLU4HFavXw=; b=KThUsSWEXfFLZfnEofZScGvuYw2tIb1NEBe2b0qYX9z53oGlDQ4F3UUjNICGuuck75 l7ytYljLMnW2m2FFiy8T+ZMGbmVHwHXByNesWvPeXxQmiXIZI0vlIHcU/sc9LA1/fDUz 2Y/XwaATtwxZZ0wShmxPCcwCpYwz/DQttoBz4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=DD6uS0hDkfA4TK+83R6IWl85YNggRmbgZKLU4HFavXw=; b=ZfMn29zK9A7SKz6P9euYqUKVvRm+EgFxGSmjn99oqrLftFZJfb9UZcgI6T5Q8eBWRT GVGakwPXjlW4c09mKRrfCB92zU+t9vkQBQRZ7CmyRg3wnXDe0hfw6L345CExMclzwAHZ Wahr17fgkhGxnHLZv8vTgezcD4KT/tz8nXTqvYaUG1Q+YPZ0A7wn+S9TsK+Tk3OIHyjn mvSswQP0N1EfciVcdp52YKoZ9HqgzDZQXirXYlj2IxC670HQFdy/dg0mJp2Kt+k3IxsW D1ne1564yRcF2c6F6Mfw9cK/9qZT/cnC+sSR0RSeNZp76YIooQ9pxflv4MDIW9AJlv4W K66w== X-Gm-Message-State: ALoCoQmnRgWJsjg3kTjBZ1kbB0y+U5EzqQIyb0241w/2RJcJ9bVhcNA727tTA/HZZFrgQqVfxO55+y492ybim9Xp4CgaAYzYPN1oSa94PyWfn1Ee7nafdaQH/uUfh+GZzA0r0UIKZIm3MOiwdIm70oKd55yxo27vHkHJiQrL/PIqqKNfmkpuk0OAEicr7EyJH3Mb0pdpcZuYTvPEJXe5GXIjQgbNqdpRhw== X-Received: by 10.66.51.137 with SMTP id k9mr16034829pao.11.1393269792684; Mon, 24 Feb 2014 11:23:12 -0800 (PST) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.68.130.198 with HTTP; Mon, 24 Feb 2014 11:22:52 -0800 (PST) In-Reply-To: References: From: Andrew Grieve Date: Mon, 24 Feb 2014 14:22:52 -0500 X-Google-Sender-Auth: mug_oNiROIJjqRXG9vs_zoX3Ink Message-ID: Subject: Re: MessageQueue seems to stop sending messages to the webView To: Don Coleman Cc: "dev@cordova.apache.org" , Andrew Grieve , james.rivett.carnac@gmail.com Content-Type: multipart/alternative; boundary=bcaec54309e811d72b04f32be772 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54309e811d72b04f32be772 Content-Type: text/plain; charset=UTF-8 Don - would be great! Seems like a pretty bad bug, so I'd love to squash it! On Mon, Feb 24, 2014 at 2:19 PM, Don Coleman wrote: > Andrew, > > I'm seeing similar behavior for a plugin I'm working on. I might be able > to get you a sample if James doesn't have one. > > - Don > > > On Mon, Feb 24, 2014 at 2:14 PM, Andrew Grieve wrote: > >> On Mon, Feb 24, 2014 at 2:14 PM, Andrew Grieve >> wrote: >> >> > James - have so far been unable to come up with a repro case for this. >> If >> > there's a chance you could create one, that would be really helpful. >> > >> > >> > On Tue, Feb 18, 2014 at 2:16 PM, Andrew Grieve > >wrote: >> > >> >> Hmm, might be same problem as >> >> https://issues.apache.org/jira/browse/CB-6047. Let's move this >> >> conversation to that bug. >> >> >> >> >> >> On Tue, Feb 18, 2014 at 2:10 AM, James Rivett-Carnac < >> >> james.rivett.carnac@gmail.com> wrote: >> >> >> >>> Hello, >> >>> >> >>> I'm uisng an embedded cordova webview and am seeing something where by >> >>> the >> >>> webview doesn't receive messages sent to it from my plugin. >> >>> >> >>> I've seen this with: >> >>> >> >>> android 4.3, 4.4.2, (Moto G, Nexus 7 2012) >> >>> cordova 3.3.0-rc1, 3.3.0-0.1.1, 3.3.1-0.4.2 >> >>> >> >>> The application is receiveing informatiion from a USB device (the >> >>> phone/tablet runs in accessory mode), reading this information in its >> own >> >>> thread. These call callbacks, and change the state in the webview >> >>> (lavaca >> >>> app). >> >>> >> >>> Generally this works without issues. Sometimes, the screen doesn't >> >>> update. If I profile the threads running, the webview is not showing >> any >> >>> activity (except maybe a call to uptime). If I unplug and plug back >> in >> >>> the >> >>> USB, the screen goes through all the pending updates (quickly flashes >> >>> through them). The app does *not* return to normal opperations at >> this >> >>> point: I have to unplug/plug back in for every message that is sent. >> If >> >>> I >> >>> do this while monitoring the threads, I see calls to the android >> message >> >>> handler happening at this point. >> >>> >> >>> When it is working correctly, these calls happen when the event is >> >>> triggered. >> >>> >> >>> My questions - what could be causing this? Is there a way to force >> the >> >>> message queue to trigger, other than unpluggin/pluggin back in? >> >>> >> >>> James >> >>> >> >> >> >> >> > >> > > --bcaec54309e811d72b04f32be772--