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.
Created attachment 17309 [details]
Screen capture of the new integrated log
New integrated log under "Tools > Android > Device Log" is dramatically less performant at reading in the log entries than the old "Android Device Logging" view, leading to loss of Visual Studio UI responsiveness until all entries have been read
## Regression status: Regression in the new Device Log as compared to the old "Android Device Logging" view
(This performance problem also affects the new iOS device log, but that feature didn't exist at all before, so it is just a "new feature" bug in that case rather than a regression.)
## Steps to replicate
1. Open an Android project in Visual Studio 2015. (Tested with Visual Studio 2015 Update 1.)
2. Ensure an Android device is attached. (Tested with an LG Optimus L9 Android 4.1 (API 16) device.)
3. Navigate to "Tools > Android > Device Log...".
4. From the "Choose Device" drop down menu, select the attached device.
## BAD Results (with the new Device Log, in VS 2015)
- After step 4, the Visual Studio UI becomes entirely non-responsive except for the updating lines in the Device Log window.
- The UI did not become responsive again until _all_ of the lines had been read from the device.
- I waited for over 5 minutes for the log lines to finish reading in. There were still many more log lines left to read. I unplugged the device to force it to stop reading lines so that I could move on to my next test.
(See attached screen capture.)
## GOOD Results with the (old Android Device Logging view, in VS 2013)
- After step 4, the Visual Studio UI becomes less responsive than normal, but it is still possible to perform operations.
- Reading in the entire logcat took approximately 22 seconds.
(See attached screen capture in next comment.)
## Version info (brief)
Visual Studio Professional 2013 Update 3
Visual Studio Professional 2015 Update 1
Windows 8.1 (64-bit)
(Running in a 2-core VM in VMWare Fusion 8.1.1, on a MacBookAir5,2 (2 GHz Core i7, I7-3667U).)
Created attachment 17310 [details]
Screen capture of the old Android Device Logging view in VS 2013
My preliminary testing on a fresh Windows 10 VM + VS 2015 Update 3 (in VMWare Fusion) shows promising results for the new Device Log. A log of more than 5000 lines loads in roughly 14 seconds in that environment, and the UI remains fairly responsive the whole time.
(For comparison, in my original Windows 8.1 VM + VS 2015 Update 1 environment, that same log shows the original "bad" behavior: after 60 seconds it only loads approximately 860 out of 5000+ lines.)
I'm fairly satisfied that we can now resolve this as upstream and record it as a known upstream issue in the Cycle 8 release notes with the recommendation that users update to the latest version of VS 2015 for the best results.
(I'll also start the VS 2015 Update 3 installation in the Windows 8.1 VM for one last check, and I will plan to update the bug once I get the results from that.)
## Verification of a resolved upstream bug in Visual Studio 2015 Update 1
BAD: Windows 8.1 VM + VS 2015 Update 1
GOOD: Windows 8.1 VM + VS 2015 Update 3
GOOD: Windows 10 VM + VS 2015 Update 3
My installation of VS 2015 Update 3 completed in the Windows 8.1 VM, and the behavior of the new Device Log is GOOD there: the log loads as quickly as on the Windows 10 VM with VS 2015 Update 3. I am accordingly resolving the issues as upstream (and also already fixed upstream).