I have to pile on to this thread because I am experiencing the EXACT same
problem on 1.2, 1.9.x, and now 4.0. I have an AsyncTask running in the
background performing a long-running task (polygon tessellation among other
things). The application crashes randomly after a period of time. If I
attempt to step into the application using the debugger I cannot isolate a
single point of failure, it varies. It does seem to be strongly correlated
to how much is being done on the background thread, shorter operations are
successful. The single constant symptom is that the crash always occurs
immediately after the monodroid garbage collector runs and is followed by an
empty stacktrace in the log. Below I have included the relevant segment of
the log, look at the entries for process ID 6349. Just like Aaron, I have
found that simpler test apps do not reproduce the problem, for me it seems
to be related to how much data my background thread is processing and how
many iterations are performed. I just noticed that 4.0.1 has been released
(*fingers crossed* :) )
12-08 17:22:13.644 D/dalvikvm( 6349): GC_EXPLICIT freed 4995 objects /
300176 bytes in 30ms
12-08 17:22:13.644 I/monodroid-gc( 6349): GC cleanup summary: 21 objects
tested - resurrecting 15.
12-08 17:22:14.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:14.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
RSSI-APPROX
12-08 17:22:14.519 D/wpa_supplicant( 1439): rssi-approx command
12-08 17:22:14.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:14.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
LINKSPEED
12-08 17:22:14.519 D/wpa_supplicant( 1439): Link Speed command
12-08 17:22:14.519 D/wpa_supplicant( 1439): buf LinkSpeed 54
12-08 17:22:17.387 D/dalvikvm( 5993): GC_EXPLICIT freed 239 objects / 14312
bytes in 36ms
12-08 17:22:17.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:17.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
RSSI-APPROX
12-08 17:22:17.519 D/wpa_supplicant( 1439): rssi-approx command
12-08 17:22:17.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:17.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
LINKSPEED
12-08 17:22:17.519 D/wpa_supplicant( 1439): Link Speed command
12-08 17:22:17.519 D/wpa_supplicant( 1439): buf LinkSpeed 54
12-08 17:22:17.777 W/PowerManagerService( 1375): Timer 0x7->0x3|0x1
12-08 17:22:17.777 I/PowerManagerService( 1375): Ulight 7->3|0
12-08 17:22:20.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:20.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
RSSI-APPROX
12-08 17:22:20.519 D/wpa_supplicant( 1439): rssi-approx command
12-08 17:22:20.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:20.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
LINKSPEED
12-08 17:22:20.519 D/wpa_supplicant( 1439): Link Speed command
12-08 17:22:20.519 D/wpa_supplicant( 1439): buf LinkSpeed 54
12-08 17:22:23.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:23.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
RSSI-APPROX
12-08 17:22:23.519 D/wpa_supplicant( 1439): rssi-approx command
12-08 17:22:23.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:23.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
LINKSPEED
12-08 17:22:23.519 D/wpa_supplicant( 1439): Link Speed command
12-08 17:22:23.519 D/wpa_supplicant( 1439): buf LinkSpeed 54
12-08 17:22:26.519 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:26.519 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
RSSI-APPROX
12-08 17:22:26.519 D/wpa_supplicant( 1439): rssi-approx command
12-08 17:22:26.527 E/wpa_supplicant( 1439): in wpa_drv_driver_cmd
12-08 17:22:26.527 D/wpa_supplicant( 1439): wpa_driver_tista_driver_cmd
LINKSPEED
12-08 17:22:26.527 D/wpa_supplicant( 1439): Link Speed command
12-08 17:22:26.527 D/wpa_supplicant( 1439): buf LinkSpeed 54
12-08 17:22:27.644 D/BatteryService( 1375): update start
12-08 17:22:27.652 D/BatteryService( 1375): updateBattery level:72 scale:100
status:4 health:2 present:true voltage: 3866 temperature: 343 technology:
Li-ion AC powered:false USB powered:true icon:17302563
12-08 17:22:27.668 D/Tethering( 1375): active iface (usb0) reported as
added, ignoring
12-08 17:22:27.668 D/WifiService( 1375): ACTION_BATTERY_CHANGED pluggedType:
2
12-08 17:22:27.668 D/BatteryService( 1375): update start
12-08 17:22:27.676 D/BatteryService( 1375): update start
12-08 17:22:29.199 I/mono ( 6349): Stacktrace:
12-08 17:22:29.199 I/mono ( 6349):
12-08 17:22:29.215 I/WindowManager( 1375): WIN DEATH: Window{48f7d828
SurfaceView paused=false}
12-08 17:22:29.223 I/ActivityManager( 1375): Process
TerragoMobileAndroid.TerragoMobileAndroid (pid 6349) has died.
12-08 17:22:29.230 I/WindowManager( 1375): WIN DEATH: Window{49007770
TerragoMobileAndroid.TerragoMobileAndroid/terragomobileandroid.TGOMobileApplication
paused=false}
12-08 17:22:29.238 I/Launcher( 1467): onResume(). mIsNewIntent : false
12-08 17:22:29.238 I/UsageStats( 1375): Unexpected resume of
com.sec.android.app.twlauncher while already resumed in
TerragoMobileAndroid.TerragoMobileAndroid
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Thread-Exceptions-Without-Stacktrace-tp5069711p5072804.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
