Bug 10549 - MonoDroid app on Intel emulator dies after 2-3 secs of start
Summary: MonoDroid app on Intel emulator dies after 2-3 secs of start
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2013-02-21 14:15 UTC by Ozge Yavuz
Modified: 2016-08-03 15:29 UTC (History)
5 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 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 FIXED

Description Ozge Yavuz 2013-02-21 14:15:41 UTC
This bug is about MonoDroid application running on Intel emulator (With latest HAXM). When I launch my application, it would die away after 2 or 3 secs of the launch unless there is some UI activity (e.g. clicking a button). This behavior is consistent and reproes all the time. This only happens on Intel emulators and does not happen when I launch a native Java application. I am on 64 bit Win8 with VS2012. 

This is a Win8 box with Visual Studio 2012. VS 2012 does not produce any errors.

Same happens if I put a breakpoint to say OnCreate(). VS will happily wait for 10 secs then disconnect from emulator, but the application would still be running – actually it would be hung on the breakpoint indefinitely.

Logcat doesn’t have any entries. But below is the c/p from output window of VS.

02-04 22:59:43.161 W/monodroid-gc( 3727): GREF GC Threshold: 1800
Loaded assembly: /data/data/TestAppllication.TestAppllication/files/.__override__/TestAppllication.dll
Loaded assembly: Mono.Android.dll [External]
Loaded assembly: System.Core.dll [External]
02-04 22:59:43.651 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:43.651 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
Loaded assembly: MonoDroidConstructors [External]
02-04 22:59:45.631 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.631 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.631 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.662 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.741 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.752 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.752 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.791 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.811 D/        ( 3727): HostConnection::get() New Host Connection established 0xb94c7e90, tid 3727
02-04 22:59:45.968 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
02-04 22:59:45.971 W/Trace   ( 3727): Unexpected value from nativeGetEnabledTags: 0
The program 'Mono' has exited with code 0 (0x0).
Comment 1 Dominique Louis 2013-06-05 13:22:35 UTC
Please retest with latest release.