incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luis Cortes (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CB-366) Bluetooth Plugin Memory Leak
Date Wed, 21 Mar 2012 16:53:42 GMT

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

Luis Cortes updated CB-366:
---------------------------


The only reason this is major, is that on my test phone, the memory leak causes my app to
terminate ( okay, the real answer of course might be to get more memory -- still there are
probably plenty of phones with lower memory constraints out there ). 
                
> Bluetooth Plugin Memory Leak
> ----------------------------
>
>                 Key: CB-366
>                 URL: https://issues.apache.org/jira/browse/CB-366
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.4.0
>            Reporter: Luis Cortes
>            Assignee: Joe Bowser
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Minor leak detected because the looper object was not released.  a simple fix can be
applied at the end of the "execute" routine before the return will clean this up.
> 		if ( Looper.myLooper() != null)
> 		{
> 			// Log.d("BluetoothPlugin", "Quit looper ...");
> 			Looper.myLooper().quit();
> 			
> 		}
> 		
> 		
> 		return result;

--
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

        

Mime
View raw message