Return-Path: 
 <callback-dev-return-5296-apmail-incubator-callback-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1230397A9
	for <apmail-incubator-callback-dev-archive@minotaur.apache.org>;
 Tue, 17 Apr 2012 21:17:38 +0000 (UTC)
Received: (qmail 12894 invoked by uid 500); 17 Apr 2012 21:17:37 -0000
Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org
Received: (qmail 12846 invoked by uid 500); 17 Apr 2012 21:17:37 -0000
Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:callback-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:callback-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:callback-dev@incubator.apache.org>
List-Id: <callback-dev.incubator.apache.org>
Reply-To: callback-dev@incubator.apache.org
Delivered-To: mailing list callback-dev@incubator.apache.org
Received: (qmail 12728 invoked by uid 99); 17 Apr 2012 21:17:37 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 21:17:37 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 21:17:33 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 4522A39F580
	for <callback-dev@incubator.apache.org>;
 Tue, 17 Apr 2012 21:17:13 +0000 (UTC)
Date: Tue, 17 Apr 2012 21:17:13 +0000 (UTC)
From: "Joe Bowser (Resolved) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <2098671822.34777.1334697433284.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <846183254.20925.1322537259989.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CB-76) PhoneGap Android JSAlerts may have a
 memory leak
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/CB-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser resolved CB-76.
--------------------------

    Resolution: Won't Fix
    
> PhoneGap Android JSAlerts may have a memory leak
> ------------------------------------------------
>
>                 Key: CB-76
>                 URL: https://issues.apache.org/jira/browse/CB-76
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: Android
>            Reporter: Simon MacDonald
>            Assignee: Joe Bowser
>             Fix For: 1.7.0
>
>
> This was discovered on a client project, and is intermittent. I wrote it off as a device issue until I ran into the same issue today on a Nexus S running CyanogenMod. Here's the issue in question!
> E/WindowManager( 4255): android.view.WindowLeaked: Activity (removed for confidentiality) has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@40586158 that was originally added here
> E/WindowManager( 4255):     at android.view.ViewRoot.<init>(ViewRoot.java:259)
> E/WindowManager( 4255):     at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:148)
> E/WindowManager( 4255):     at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:91)
> E/WindowManager( 4255):     at android.view.Window$LocalWindowManager.addView(Window.java:465)
> E/WindowManager( 4255):     at android.app.Dialog.show(Dialog.java:241)
> E/WindowManager( 4255):     at android.app.AlertDialog$Builder.show(AlertDialog.java:812)
> E/WindowManager( 4255):     at com.phonegap.DroidGap$GapClient.onJsAlert(DroidGap.java:824)
> E/WindowManager( 4255):     at android.webkit.CallbackProxy.handleMessage(CallbackProxy.java:501)
> E/WindowManager( 4255):     at android.os.Handler.dispatchMessage(Handler.java:99)
> E/WindowManager( 4255):     at android.os.Looper.loop(Looper.java:130)
> E/WindowManager( 4255):     at android.app.ActivityThread.main(ActivityThread.java:3835)
> E/WindowManager( 4255):     at java.lang.reflect.Method.invokeNative(Native Method)
> E/WindowManager( 4255):     at java.lang.reflect.Method.invoke(Method.java:507)
> E/WindowManager( 4255):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
> E/WindowManager( 4255):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
> E/WindowManager( 4255):     at dalvik.system.NativeStart.main(Native Method)
> This happens when people are using an Alert in a callback, in this case the reachability API. I'm going to investigate this further, but its the reason there's the infamous "The connection to the server was unsuccessful" is happening.
> Of course, once you kill it and restart the app, the problem goes away, but this doesn't provide a great user experience. I'll assign this to myself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira