Bug 59897 - debug stops on LG-440AR, then app stop
Summary: debug stops on LG-440AR, then app stop
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 5.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
: 60292 ()
Depends on:
Reported: 2017-10-02 15:03 UTC by Francisco
Modified: 2017-11-14 01:26 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Logcat (147.81 KB, text/plain)
2017-10-02 19:50 UTC, Francisco
Logcat (140.88 KB, text/plain)
2017-10-02 20:33 UTC, Francisco
Droid INFO (2.57 KB, text/plain)
2017-10-02 21:31 UTC, Francisco

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Francisco 2017-10-02 15:03:54 UTC
I am running my app on lollipop 5.0.1 on samsung phones and emulators without any problems.

When i run on LG 440 spirit the app hangs up and get killed without generate a crash.

The app starts an intent for the camera and when it cames back in some point the original app get killed.

I see the same occurs with any others applications. I think its a memory usage / app restart problem

If i switch to youtube, maps, etc, when i came back to the app it gets stupid and then get a message "the app has stoped".

I enabled azure crash tracking but nothing is generated.

When I debbuged the app with the physical phone with xamarin studio at some point (i think increase memory usage) i lost debug connection and then the app stops, so i cant get any clue. (I am debugging over tcpip)

As a difference with samsung or emulators when i run on LG i get a lot of tgis messages in the log window:

[BubblePopupHelper] isShowingBubblePopup : false

[BubblePopupHelper] isShowingBubblePopup : false

[BubblePopupHelper] isShowingBubblePopup : false

[BubblePopupHelper] isShowingBubblePopup : false

[BubblePopupHelper] isShowingBubblePopup : false

[BubblePopupHelper] isShowingBubblePopup : false

I not sure if this is somthing related or not

=== Xamarin Studio Community ===

Version 6.3 (build 863)
Installation UUID: 19241863-49bd-442b-b9e9-45b5ca2b6588
	Microsoft .NET 4.0.30319.42000
	GTK+ 2.24.26 (Light theme)
	GTK# 2.12.38

=== NuGet ===


=== Xamarin.Profiler ===

'/Applications/Xamarin Profiler.app' not found

=== Xamarin.Android ===

Versión: (Xamarin Studio Community)
Android SDK: C:\Program Files (x86)\Android\android-sdk
	Versiones de Android admitidas:
		4.4 (nivel de API 19)
		5.0 (nivel de API 21)
		5.1 (nivel de API 22)
		6.0 (nivel de API 23)
		7.1 (nivel de API 25)

Versión de las herramientas del SDK: 24.4.1
Versión de las herramientas de plataforma del SDK: 23.0.1
Versión de las herramientas de compilación del SDK: 23.0.1

Java SDK: C:\Program Files\Java\jdk1.8.0_144
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

El código EPL de Android Designer está disponible EPL:

=== Build Information ===

Release ID: 603000863
Git revision: a2163670efe259c85cd8f335d95b175068fbbe2a
Build date: 2017-04-03 13:27:10-04
Xamarin addins: 2045d688ea1420e0381b473360ca62a763eb7d04
Build lane: monodevelop-windows-d15-1

=== Operating System ===

Windows 6.3.9600.0 (64-bit)
Comment 1 Jon Douglas [MSFT] 2017-10-02 15:21:05 UTC
Hi Francisco,

Firstly, it seems like you are on some quite older builds in comparison to our Stable channel of updates. Can you please update your environment to Visual Studio for Mac and use the Stable channel of updates to get the latest stable builds?


The installer should leave you off with the latest stable updates. In case you need to update, you can view this documentation:


As a means of trying to debug this issue, we will want to know a bit more about this device. A few google searches did not help me identify this phone's specs. Can you please provide the device specifications such as:

OS Version / SDK Version
CPU Architecture / Chipset
Total RAM

You can download an application from the Google Play Store such as "Droid Info" / "Device Info" which should have all of this information and you can even export these items to text.

Finally, we will want an "adb logcat" that has the crash included. You can open up a Device Monitor or use the command line logcat tool to continuously generate logging from your device until you reproduce the crash. Here's further instructions on this item:

Comment 2 Francisco 2017-10-02 19:48:12 UTC
I am on windows so i switched to visual studio

Microsoft Visual Studio Community 2015
Versión 14.0.25425.01 Update 3
Microsoft .NET Framework
Versión 4.7.02053

Versión instalada: Community

Visual Basic 2015   00322-20000-00000-AA549
Microsoft Visual Basic 2015

Visual C# 2015   00322-20000-00000-AA549
Microsoft Visual C# 2015

Visual C++ 2015   00322-20000-00000-AA549
Microsoft Visual C++ 2015

Windows Phone SDK 8.0 - ESN   00322-20000-00000-AA549
Windows Phone SDK 8.0 - ESN

Administrador de paquetes NuGet   3.4.4
Administrador de paquetes NuGet de Visual Studio. Para obtener más información acerca de NuGet, visite http://docs.nuget.org/.

ASP.NET Web Frameworks and Tools 2012.2   4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET Web Frameworks and Tools 2013   5.2.40314.0
For additional information, visit http://www.asp.net/

ASP.NET y herramientas web 2015.1 (Beta8)   14.1.11107.0
ASP.NET y herramientas web 2015.1 (Beta8)

Herramientas comunes de Windows Azure   1.8
Ofrece servicios comunes para su uso con los servicios móviles de Microsoft Azure y Microsoft Azure Tools.

Herramientas de servicios móviles de Microsoft Azure   1.4
Herramientas de servicios móviles de Microsoft Azure

Merq   1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.

Mono Debugging for Visual Studio   4.6.8-pre (ec7034f)
Support for debugging Mono processes with Visual Studio.

Paquete Herramientas de Application Insights para Visual Studio   7.18.00214.2
Herramientas de Application Insights para Visual Studio

PreEmptive Analytics Visualizer   1.2
Extensión de Microsoft Visual Studio para visualizar los resúmenes agregados desde el producto PreEmptive Analytics.

Servicio de lenguaje JavaScript   2.0
Servicio de lenguaje JavaScript

Sistema del proyecto JavaScript   2.0
Sistema del proyecto JavaScript

SQL Server Data Tools   14.0.60519.0
Microsoft SQL Server Data Tools

Herramientas de TypeScript para Visual Studio

Visual Studio Tools para las Aplicaciones Windows universales   14.0.25527.01
Las herramientas Visual Studio Tools para las Aplicaciones Windows universales permiten crear una experiencia de aplicación universal sencilla para todos los dispositivos que ejecutan Windows 10: teléfono, tableta, PC y más. Incluye el kit de desarrollo de software de Microsoft Windows 10.

Xamarin (bd7e3753c)
Extensión de Visual Studio para habilitar la implementación de Xamarin.iOS y Xamarin.Android.

Xamarin.Android (fb018c5)
Extensión de Visual Studio que permite el desarrollo de Xamarin.Android.

Xamarin.iOS (152b654)
Extensión de Visual Studio para habilitar la implementación de Xamarin.iOS.
Comment 3 Francisco 2017-10-02 19:50:18 UTC
Created attachment 25057 [details]

You have phone info in the log of mobile center startup
Comment 4 Francisco 2017-10-02 19:58:03 UTC
Comment on attachment 25057 [details]

The log is until the app starts an intent for the camera, then debugger disconnects and some time later when i came back to the app the app says "app has stoped" and do not generate crash info.

When i start the app again its supposed that the crash info goes to mobile center, but not.
Comment 5 Francisco 2017-10-02 20:33:57 UTC
Created attachment 25060 [details]
Comment 6 Francisco 2017-10-02 21:31:21 UTC
Created attachment 25061 [details]
Droid INFO
Comment 8 Jon Douglas [MSFT] 2017-10-24 16:26:59 UTC
Hi Francisco,

I do not see any logs indicating the following:

1. Your application being killed
2. The debugger trying to connect

Can you please be sure that your adb logcat is continuously running before you reproduce this issue with the device? You can use the "Tool -> Device Monitor" or "View -> Pads -> Device Log" to get a continuous logcat of your device. We are especially interested in the logs that are filtered with the "error" tag.

Ideally we should see at least the package of your application and an "ActivityMonitor" tag.
Comment 9 Jon Goldberger [MSFT] 2017-10-24 22:05:37 UTC
*** Bug 60292 has been marked as a duplicate of this bug. ***
Comment 10 Francisco 2017-10-24 22:49:33 UTC

I have answered the info on the 60292 that is a run for the xamarincrm app from your web sample pages.
Comment 11 Jon Douglas [MSFT] 2017-11-14 01:26:52 UTC
I can't exactly tell what's going on with your device and application. It does seem to have traces of a potential memory leak or too much work being done on the UI thread. I have a blog on this topic that may help out:


The log you have provided does not have any mention of "ActivityManager" which would show us the activity is being killed. Also there is no mention of an "ANR" which means the application is not responding due to too much work on the main thread.

I do believe this logcat was cut off short.

However I did look at a logcat in the duplicate bug and found the following:

10-24 19:20:41.001: I/WindowState(1435): WIN DEATH: Window{36707a91 u0 com.xamarin.xamarincrm/md51509fcfd2c5811b7644dd69ffcb09fb1.MainActivity}

WIN DEATH is typically due to an ANR (Activity Not Responding) in which my blog helps identify and resolve these problems. It is usually a symptom that your application's process is exiting for some reason(OS, Root App, Force Close, etc). Given there's no other mention of the app being killed in the logs, I would suspect an ANR that was skipped over and not logged to logcat.

There is also a great article on this topic you can find here:


Some other things that you might want to try other than optimizing your app if the code is already simple:

Make sure not many other apps are running at the same time. It is possible the OS could be killing your app