Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I have experienced this issue before with other projects, but it is now a consistent problem with the work I am doing on the Caulker project.
I am debugging the app on my device (Samsung Galaxy S2), using Visual Studio 2010.
To repo the issue, grab the code from my Github and run the demo project.
Within 5 - 30 seconds of the app starting, the debugger dies silently. Nothing shows in the Android adb trace except the "Window died" messages.
I suspect it may have something to do with the threading involved in the tile downloads.
The other projects where this debugger issue has happened also involve Http requests in asynch (multi-threaded) scenarios.
Note: the app generally runs fine directly off the phone (i.e. without debugger).
I cannot reproduce this on my Nexus One. I'll ask around and see if someone has a Samsung device that can try this to see if it's device specific.
If you want to help narrow it down further, you can comment out pieces of your thread code until it stops crashing.
Created attachment 2051 [details]
Here's a test case that allows me to reproduce this in Visual Studio 2010 with my Nexus One.
Fixed for 4.2.4.
Thanks for the report!
*** Bug 2945 has been marked as a duplicate of this bug. ***
*** Bug 5801 has been marked as a duplicate of this bug. ***