Bug 26581 - [Android] App crashes on device shortly after login, possibly due to low memory
Summary: [Android] App crashes on device shortly after login, possibly due to low memory
Status: RESOLVED ANSWERED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.20.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
: 26692 ()
Depends on:
Blocks:
 
Reported: 2015-01-29 19:12 UTC by Kent Green [MSFT]
Modified: 2015-02-20 12:30 UTC (History)
2 users (show)

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

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:
Status:
RESOLVED ANSWERED

Description Kent Green [MSFT] 2015-01-29 19:12:10 UTC
---Overview---
From this desk case:
https://xamarin.desk.com/agent/case/120228

Customer's app crashes on device shortly after login, possibly due to low memory. Based on the customer's sample, I was able to reproduce the issue. Specifically, while the app doesn't crash in the Genymotion API 19 emulator; it freezes immediately after login on my test device; an LG Volt Android API 19 device. 

The customer also reports that on different devices, the crash would also occur after login, but at different times. Specifically, on their Galaxy S3 test device, they report that it would crash after clicking on a few menus. Their test on a Galaxy S5 would take a bit longer to crash.


=== Xamarin Studio ===

Version 5.7 (build 661)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
Runtime:
	Mono 3.12.0 ((detached/a813491)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000068

=== Apple Developer Tools ===

Xcode 6.1.1 (6611)
Build 6A2008a

=== Xamarin.iOS ===

Version: 8.6.0.51 (Business Edition)
Hash: dfb682f
Branch: 
Build date: 2015-01-08 13:39:32-0500

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/kentgreen/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Build Information ===

Release ID: 507000661
Git revision: b70bab61da996da29045ea8ee8aed1a6faedbe78
Build date: 2015-01-05 16:31:31-05
Xamarin addins: 82f6c71490562d6cd125a09287f441902fdac3d7

=== Operating System ===

Mac OS X 10.10.1
Darwin Kents-MacBook-Pro-2.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64

---Additional info---
Since the sample is from a customer, I will add it & the logs as a private attachment shortly.
Comment 2 Kent Green [MSFT] 2015-02-03 11:52:44 UTC
*** Bug 26692 has been marked as a duplicate of this bug. ***
Comment 7 Kent Green [MSFT] 2015-02-20 12:30:28 UTC
Customer originally reporting issue in case #120228 noted that with the fixes to the code as noted in private comments 4-6 resolved the issue, and they are no longer seeing the problem. 
(Note: Those comments are private due to relating to user-specific code.)

As such, marking this bug RESOLVED ANSWERED.