Bug 8807 - Android Device Logging view causes freezes and slow down.
Summary: Android Device Logging view causes freezes and slow down.
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-12-06 11:21 UTC by Al
Modified: 2015-08-24 09:23 UTC (History)
7 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Al 2012-12-06 11:21:00 UTC
if the android device prints a lot of messages to LogCat it will start to slow down visual studio. If I clear the contents of device logging view then V.S. returns to its usual performance. 

If I leave it spamming for long enough it renders VS completely unusable and requires killing via task manager. 

I'm using VS 2010 and the latest version of mono with android device logging in list view mode. 
(i've seen this behaviour in all the versions of m4a i've used.)
Comment 1 Rajneesh Kumar 2015-07-21 10:09:21 UTC
Could you please check this issue with the latest stable build XVS 3.11.666 and let us know that its working for you OR you are till getting same behaviour ?

Comment 2 Abhishek 2015-08-03 13:04:46 UTC
There is no response from the reporter. So as if 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.