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.
Seen in this forum discussion: http://forums.xamarin.com/discussion/558/vs-2012-slows-down-or-even-freezes-after-debugging-session-or-after-running-without-debug#latest
After installing Mono for Android 4.4.50, results in slowness and freezing after debug session or run without debugging.
- WinXP Professional (32Bit) SP 3
- Intel Core i3 / 2GB RAM
- VS2010 SP1, but occurs in VS2012 as well
The slowness makes itself noticeable by:
- very slow build (> 30 sec.) after 3-4 debug sessions
- can't debug after the 3.-4. debug session
- when pressing a key on the keyboard the pressed key appears after 2-3sec. on the monitor (after the 5-6 debug session)
- then th VS needs more than 600MB memory - when I'm doing nothing (at times also more than 800MB)
I'm having similar issues (Mono for Android 4.6)
VS freezes when starting to debug, when stopping to debug
when trying to edit AXML files, when switching between source files.
Only when working on Mono for Android projects. Freezes can take up to a few minutes, sometimes I'm forced to kill Visual Studio.
CPU usage raises to 20% for child process of Visual Studio
- Windows 7 Ultimate
- Intel Xeon Dual Quad Core CPU / 12GB RAM
If you kill adb.exe Visual Studio resumes... of course that means your debug session is disconnected as well.
Could you please check this issue with the latest stable build XVS 3.11.666 and please check its working for you OR you are till getting same behaviour ?
There is no response from the reporter. So as of now I am closing this issue against stable build XVS 3.11.666. Please feel free to reopen this issue if you again facing this behavior at your end.
Hence Closing this issue.
not reproducible in xma 184.108.40.2067