AbdFatah / analytics-issues

Automatically exported from code.google.com/p/analytics-issues
0 stars 0 forks source link

Android library causes 100% CPU usage under bad network conditions #223

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Name of affected component: Mobile Tracking

Name of related library and version, if applicable (e.g. Android, iOS,
Snippets, etc.): Analytics Android SDK 1.4.2

Issue summary:
Provide a brief summary of the issue you're experiencing.

Steps to reproduce issue:
1. Use the library in your Android app
2. Have a network problem
3. Sometimes (this is not reproducible all the time), there seems to be a 
infinite loop, which causes the app to use 100% of the CPU.

Notes:
Here is what I see when dumping the UI thread:

android.os.BinderProxy  transact    Binder.java -2  true    
android.net.IConnectivityManager$Stub$Proxy getActiveNetworkInfo    IConnectivityMa
nager.java  670 false   
android.net.ConnectivityManager getActiveNetworkInfo    ConnectivityManager.java    71
2   false   
com.google.android.apps.analytics.GoogleAnalyticsTracker    dispatch        -1  false   
com.google.android.apps.analytics.GoogleAnalyticsTracker$1  run     -1  false   
android.os.Handler  handleCallback  Handler.java    605 false   
android.os.Handler  dispatchMessage Handler.java    92  false   
android.os.Looper   loop    Looper.java 154 false   
android.app.ActivityThread  main    ActivityThread.java 4944    false   
java.lang.reflect.Method    invokeNative    Method.java -2  true    
java.lang.reflect.Method    invoke  Method.java 511 false   
com.android.internal.os.ZygoteInit$MethodAndArgsCaller  run ZygoteInit.java 784 f
alse    
com.android.internal.os.ZygoteInit  main    ZygoteInit.java 551 false   
dalvik.system.NativeStart   main    NativeStart.java    -2  true    

The UI thread seems to stay in this state constantly.
It is my understanding that the library must be calling the 
"GoogleAnalyticsTracker.dispatch" method in a loop.  I suppose this is due to 
the connectivity problem.

Since this call is not in our code I don't know how to work around this issue 
(other than stopping using Analytics).

Original issue reported on code.google.com by BoDl...@gmail.com on 5 Jul 2012 at 2:12

GoogleCodeExporter commented 9 years ago
Pertains to legacy v1.x of SDK, closing as obsolete. Please upgrade to v3.x or 
higher.

Original comment by awa...@google.com on 8 Nov 2013 at 11:47