[mono-android] Thread Exceptions Without Stacktrace

[chris@Terrago]

Happy new year everyone! I believe I have a sample app that demonstrates this
problem. I isolated the sections of code that caused the problem for me into
a smaller demo app that produces the same type of exception immediately
after the mono GC runs on the thread.

01-03 16:35:24.570 F/        ( 4673): * Assertion: should not be reached at
../../../../mono/metadata/sgen-marksweep.c:279
01-03 16:35:24.570 I/mono    ( 4673): Stacktrace:
01-03 16:35:24.570 I/mono    ( 4673): 
01-03 16:35:24.570 I/mono    ( 4673):   at System.Array.Resize<T> (T[]&,int)
<0x00077>
01-03 16:35:24.586 I/ActivityManager( 1378): Process
CrashTestDummy.CrashTestDummy (pid 4673) has died.

As you can see from the log excerpt the exception in the demo is not always
stacktrace-less, as Steve observed, but does not always occur in the same
place either. It is also important to note that the stacktrace and assertion
messages only appear when running in RELEASE. I do believe it is indicative
of the same underlying problem. To further simplify the situation I am using
only the UI thread, no worker threads.

Jonathan, I would like to get you this code ASAP. Where should I send it?
Shall I attempt to zip and email it or do you have an upload site I can use?

Thanks,
Chris


--
View this message in context: http://mono-for-android.1047100.n5.nabble.com/Thread-Exceptions-Without-Stacktrace-tp5069711p5118177.html
Sent from the Mono for Android mailing list archive at Nabble.com.