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.
On my machine Android Log View makes devenv.exe consume 100% CPU for several minutes on end after launching the application. Eventually (after the log grows too much) it completely locks up VS. This happens even if the log window is invisible or closed.
The problem can be temporarily mitigated by making the log view stop logging. This immediately removes CPU load. Unfortunately, logging is automatically re-enabled with every application launch. If I forget to promptly disable it, it will quickly hang VS. This is rather annoying, as I have to kill and restart VS with pretty much every application launch.
Please note: this happens even if log view is hidden or closed. Does not make any difference.
Fix suggestion: add an option to disable Android Log View, or at least make the log view not start automatically if the application is launched, allowing me to disable it once and for good.
Personally, I prefer viewing the log through adb logcat running in console anyway because it's much faster.
I have checked this issue but I am not able to reproduce this issue. Could you please recheck this issue on latest build and Please let we know if you getting same behavior on latest build.
Marking as resolved not_reproducible.
Please feel free to reopen the issue if you can still reproduce it with current bits.