This should be fixed for 4.2.4. I wanted to tremendously thank you for
this test case. This is what led us to be able to fix it.
For reference, the issue is that the GC process was causing our debugger
'keep-alives' to not fire. When VS didn't hear back from the runtime
after a timeout, it assumed the process was hung and it killed the
debugger and the application.
The workarounds until 4.2.4 is available are:
- Don't trigger a GC collection more than every ~5 seconds.
- Run without debugging (Ctrl-F5).
- Debug in MonoDevelop rather than Visual Studio.
Thanks again for finding a solid test case for this, it made all the
difference for fixing this long standing heisenbug. :)
Jonathan
On 6/13/2012 3:19 AM, l0nestar wrote:
Spoke too soon.. :(
However i think i can create a very similar issue in the default android
opengl app.
If you create a new monodroid opengl project and then put these lines in
GLView#.cs OnRenderFrame, underneath GL.DrawArrays():
for (int i = 0; i < 50; i++)
GC.Collect(0);
For me it exits after a few seconds. However if I run the app without the
debugger it runs fine.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/debugger-constantly-detaches-tp5710262p5710313.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
