Bug 2219 - Error occurs when user start the application "JetBoy" on Emulator.
Summary: Error occurs when user start the application "JetBoy" on Emulator.
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Android
Classification: Xamarin
Component: Samples ()
Version: 4.0
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Oleg Demchenko
URL:
Depends on:
Blocks:
 
Reported: 2011-11-28 07:34 UTC by narayanp
Modified: 2014-01-14 15:05 UTC (History)
8 users (show)

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


Attachments
Stacktrace of Windows 7 (1.53 KB, text/plain)
2012-01-12 08:54 UTC, Atin
Details
Stacktrace for the bug (3.04 KB, text/rtf)
2012-01-12 08:58 UTC, Atin
Details
Stacktrace for this issue (3.34 KB, text/rtf)
2012-01-12 10:32 UTC, Saurabh
Details


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 NOT_REPRODUCIBLE

Description narayanp 2011-11-28 07:34:50 UTC
Step To Reproduce:

1.Launch the MonoDevelop.
2.Click on "Start a New Solution" link.
3.Choose C# > Mono for Android in left hand panel.
4.Select Mono for Android Application from the center panel.
5.Open the solution for the sample application "JetBoy".
6.Build then Run the application on API10.
9.Observe that error appears.

Actual result:
Application launched successfully on the simulator and when user click on Start button to run the app, application getting crashed.

Expected result:
Error should not appear and the application should run successfully.

Environment:
MonoDevelop 2.8.2 with Addin 3.9.9.4
Mono for Android 4.0
Windows 7
Mac 10.6 (Snow Leopard)
Mac 10.7 (Lion)
Comment 1 Jonathan Pobst 2011-11-28 18:05:11 UTC
Can you please attach the text or screenshot of the error?  Thanks!
Comment 2 Jonathan Pryor 2011-11-29 15:46:39 UTC
What simulator are you deploying this to?
Comment 3 narayanp 2011-12-22 06:35:42 UTC
We are trying on API10,API7 and API14.
Comment 4 narayanp 2012-01-10 08:48:29 UTC
We RUN this application on API 14 (Build Target Android 4 Ice Cream Sandwich) and API 10 (Build Target Android 2.3 Gingerbread), we noticed that application launch successfully, but gets crashed when we click on START button.

Environments:
Mono Develop 2.8.6 Beta
Mono for Android 4.0.2  Beta 
Windows 7
Comment 5 Atin 2012-01-12 08:52:48 UTC
We have download the sample applications through the below link:
https://github.com/xamarin/monodroid-samples/tree/monodroid-4.0.2

Today, using the following environment:

Windows 7
MonoDevelop 2.8.6 Beta
Mono for Android 4.0.3 Beta

We Run this application on API-10 API-12 and API-14 using the BUILDTARGET={Gingerbread, Honeycomb, and Ice cream sandwitch} respectively. It is working fine on API-10 and API-12. However, on API-14 the application launch successfully, but as soon as we click on Start button it crashes.

We have attached the stacktrace "Win7_Jet boy_API-14_Stacktrace.txt" of the error in this bug.

The test case ID as well as its testrail link is mentioned below:

ID: T24565
Link: https://testrail.xamarin.com/index.php?/tests/view/24565
Comment 6 Atin 2012-01-12 08:54:27 UTC
Created attachment 1171 [details]
Stacktrace of Windows 7
Comment 7 Atin 2012-01-12 08:57:38 UTC
We have downloaded the M4A sample application packages from below link:
https://github.com/xamarin/monodroid-samples/tree/monodroid-4.0.2

We RUN this application On API 10, 12 and 14 on Build target (Gingerbraed, Honeycomb and Ice Cream) respectively, application ran successfully on API 12 , but on API 10 and API14 it chrased when we click on START button.

Please get the attached stack trace "SnowLeopardStackTrace.rtf"for the same.

Environments:
Mono Develop 2.8.6(Beta)
Mono For Android 4.0.3(Beta)
Mono Framework2.10.8(Stable)
Mac OSX 10.6 Snow Leopard

Test Case link:
https://testrail.xamarin.com/index.php?/tests/view/24535
Comment 8 Atin 2012-01-12 08:58:15 UTC
Created attachment 1172 [details]
Stacktrace for the bug
Comment 9 Saurabh 2012-01-12 10:30:26 UTC
We are getting this issue on Lion

Environments:
Mono Develop 2.8.6(Beta)
Mono For Android 4.0.3(Beta)
Mono Framework2.10.8(Stable)
Mac OSX 10.6 Lion

Test case link:
https://testrail.xamarin.com/index.php?/tests/view/24550
Comment 10 Saurabh 2012-01-12 10:31:21 UTC
We are getting this issue on Lion

Environments:
Mono Develop 2.8.6(Beta)
Mono For Android 4.0.3(Beta)
Mono Framework2.10.8(Stable)
Mac OSX 10.7 Lion

Test case link:
https://testrail.xamarin.com/index.php?/tests/view/24550
Comment 11 Saurabh 2012-01-12 10:32:24 UTC
Created attachment 1173 [details]
Stacktrace for this issue
Comment 12 Jonathan Pryor 2012-01-12 22:02:50 UTC
The question is this: is this a regression?

The answer: I don't know.

Firstly, I don't fully understand Comment #7. What I think it's saying is that running an API 10 build on an API 10 device works, an API 12 build on an API 12 device works, and an API 14 build on a API 14 device fails. Is this correct?

Secondly, just to make matters "interesting," FOR ME, on OS X, an API 14 build runs on an API 14 device without error. An API 8 build also runs without error on an API 14 device. Thus, there is no failure, and no regression, on my machine. :-/

It could plausibly be a Windows build issue...but is it a regression? To find out, someone will need to install Mono for Android 4.0 and run the same configuration against 4.0.0. Does an API 14 build on an API 14 device with Mono for Android 4.0.0 run or fail? If it runs, it's a regression; if it fails, it's not a regression, though it would be an unfortunate (and inexplicable) difference between the Windows and OS X builds.

Unfortunately I can't easily try that test, as my Windows box is down for the moment.

For comparison, here's the logcat output from my run. Note that there are no "Clamp target" messages, error messages from dalvikvm-heap, or messages from skia (as Attachment 1173 [details] contains):

> I/ActivityThread( 1199): Pub JetBoy.JetBoy.__mono_init__: mono.MonoRuntimeProvider
> D/dalvikvm( 1199): Trying to load lib /data/data/JetBoy.JetBoy/lib/libmonodroid.so 0x40f973b0
> D/dalvikvm( 1199): Added shared lib /data/data/JetBoy.JetBoy/lib/libmonodroid.so 0x40f973b0
> I/monodroid-gc( 1199): environment supports jni NewWeakGlobalRef
> D/JetBoy  ( 1199): opening jet file
> D/JetBoy  ( 1199): opening jet file DONE
> D/JetBoy  ( 1199):  start queuing jet file
> D/JetBoy  ( 1199):  start queuing jet file DONE
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 66K, 10% free 5811K/6403K, paused 47ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 6.620MB for 566416-byte allocation
> D/dalvikvm( 1199): GC_CONCURRENT freed <1K, 9% free 6363K/6983K, paused 3ms+3ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 553K, 17% free 6121K/7303K, paused 27ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 7.261MB for 921616-byte allocation
> D/dalvikvm( 1199): GC_CONCURRENT freed <1K, 16% free 7021K/8263K, paused 3ms+3ms
> D/dalvikvm( 1199): GC_CONCURRENT freed 900K, 20% free 6628K/8263K, paused 3ms+5ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 20% free 6628K/8263K, paused 28ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 7.756MB for 921616-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 9% free 7527K/8263K, paused 26ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 0K, 9% free 7528K/8263K, paused 28ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 8.250MB for 518416-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 0K, 9% free 8034K/8775K, paused 29ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 1286K, 20% free 7354K/9159K, paused 27ms
> D/dalvikvm( 1199): GC_CONCURRENT freed 261K, 18% free 7583K/9159K, paused 3ms+4ms
> I/WindowManager(   79): createSurface Window{418f0718 JetBoy.JetBoy/jetboy.JetBoyActivity paused=false}: DRAW NOW PENDING
> I/WindowManager(   79): createSurface Window{41907f90 SurfaceView paused=false}: DRAW NOW PENDING
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 290K, 17% free 7676K/9159K, paused 32ms
> D/gralloc_goldfish( 1199): Emulator without GPU emulation detected.
> D/dalvikvm( 1199): GREF has increased to 201
> D/dalvikvm( 1199): GC_CONCURRENT freed 5K, 11% free 8224K/9159K, paused 3ms+4ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 11% free 8224K/9159K, paused 29ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 8.975MB for 565776-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 10% free 8776K/9735K, paused 27ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 3K, 10% free 8781K/9735K, paused 30ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 9.859MB for 921616-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 10% free 9680K/10695K, paused 27ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 900K, 18% free 9287K/11207K, paused 28ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 13% free 9840K/11207K, paused 28ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 10.893MB for 921616-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 12% free 10739K/12167K, paused 26ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed 900K, 19% free 10346K/12679K, paused 29ms
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 15% free 10899K/12679K, paused 27ms
> I/dalvikvm-heap( 1199): Grow heap (frag case) to 11.588MB for 566416-byte allocation
> D/dalvikvm( 1199): GC_FOR_ALLOC freed <1K, 14% free 11452K/13255K, paused 27ms
> W/TextLayoutCache( 1199): computeValuesWithHarfbuzz -- need to force to single run
> D/JetBoy  ( 1199): ------> STARTING JET PLAY
> D/jpobst  ( 1199): 1:11
> D/jpobst  ( 1199): 1:10
> D/InputEventConsistencyVerifier( 1199): KeyEvent: ACTION_UP but key was not down.
> D/InputEventConsistencyVerifier( 1199):   in com.android.internal.policy.impl.PhoneWindow$DecorView@40fa2618
> D/InputEventConsistencyVerifier( 1199):   0: sent at 7468912000000, KeyEvent { action=ACTION_UP, keyCode=KEYCODE_DPAD_CENTER, scanCode=232, metaState=0, flags=0x8, repeatCount=0, eventTime=7468912, downTime=7468912, deviceId=0, source=0x301 }
> D/InputEventConsistencyVerifier( 1199):   -- recent events --
> D/InputEventConsistencyVerifier( 1199):   1: sent at 7465192303000, MotionEvent { action=ACTION_UP, id[0]=0, x[0]=171.0, y[0]=218.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=7465192, downTime=7465192, deviceId=0, source=0x1002 }
> D/InputEventConsistencyVerifier( 1199):   2: sent at 7465192248000, MotionEvent { action=ACTION_DOWN, id[0]=0, x[0]=171.0, y[0]=218.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=7465192, downTime=7465192, deviceId=0, source=0x1002 }
> D/InputEventConsistencyVerifier( 1199):   3: sent at 7461730266000, MotionEvent { action=ACTION_UP, id[0]=0, x[0]=155.0, y[0]=213.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=7461730, downTime=7461713, deviceId=0, source=0x1002 }
> D/InputEventConsistencyVerifier( 1199):   4: sent at 7461713794000, MotionEvent { action=ACTION_DOWN, id[0]=0, x[0]=155.0, y[0]=213.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=7461713, downTime=7461713, deviceId=0, source=0x1002 }
> D/jpobst  ( 1199): 1:09
> D/jpobst  ( 1199): 1:08
> D/jpobst  ( 1199): 1:07
> D/jpobst  ( 1199): 1:06
> D/jpobst  ( 1199): 1:05
> D/jpobst  ( 1199): 1:04
> D/jpobst  ( 1199): 1:03
> D/jpobst  ( 1199): 1:02
> D/jpobst  ( 1199): 1:01
> D/jpobst  ( 1199): 1:00
> D/jpobst  ( 1199): 0:59
> D/jpobst  ( 1199): 0:58
> D/jpobst  ( 1199): 0:57
> D/jpobst  ( 1199): 0:56
> D/jpobst  ( 1199): 0:55
> D/jpobst  ( 1199): 0:54
> D/jpobst  ( 1199): 0:53
> D/dalvikvm( 1199): GREF has increased to 301
> D/jpobst  ( 1199): 0:52
> D/jpobst  ( 1199): 0:51
> D/jpobst  ( 1199): 0:50
> D/jpobst  ( 1199): 0:49
> W/IInputConnectionWrapper( 1199): showStatusIcon on inactive InputConnection
Comment 13 Eric Beisecker 2012-01-13 10:22:54 UTC
I think Atin was saying that API level 12 was the only one that worked.

Last week I was able to run the JetBoy application on API level 14 with Mono For Android 4.0.1 but now with Mono For Android 4.0.3 this application Crashes.
Comment 14 Jonathan Pobst 2012-01-13 10:31:24 UTC
I get the same error in the API level 10 emulator in 4.0.1, so this doesn't look like a regression from the previous version.
Comment 15 Jonathan Pobst 2012-01-13 10:51:36 UTC
Also fails on 4.0. (emulator-10)
Comment 16 Oleg Demchenko 2014-01-14 15:05:24 UTC
Works fine with API 10 level emulator: http://screencast.com/t/Q97iNhta

Environment details:
OS X 10.9.1
XS Version 4.2.2
Xamarin.Android 4.10.2