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 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.
1. Create an application.
2. Set a breakpoint somewhere.
3. Debug the app.
4. Hit the breakpoint.
5. Walk away from Visual Studio for, oh, 30 minutes (get coffee, etc.).
Expected results: the debugger should still be attached, waiting for you.
Actual results: The process has died, and the debugger is now useless.
I can't replicate this on the latest master of andorid and vs.
I left an opengl app sitting on a break point over lunch, when I got back the android screen was black as was the windows (The machine had not gone to sleep though). got into vs and clikced step over, and it stepped over ok. clicked run and it continued the app in a paused state (as expected) woke up the android device and the break point hit again.
This was on a Nexus 4, also tested on the genymotion emulator with the same results. I'll try on some older devices in case its a android version issue.
nope , still can't replicate this one on the latest master builds.
Tried on a number of devices and simulators.
Given it cannot be reproduced with latest bits bug as resolved fixed.