Bug 1713 - VS crashes when filtering device log
Summary: VS crashes when filtering device log
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Highest normal
Target Milestone: ---
Assignee: Jose Miguel Torres
URL:
Depends on:
Blocks:
 
Reported: 2011-10-27 05:14 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2016-08-03 15:24 UTC (History)
10 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Rolf Bjarne Kvinge [MSFT] 2011-10-27 05:14:32 UTC
Repro:
Create and Run project from template (Mono for Android Application)
Show the Android device log.
Change the filter to something besides None (ActivityManager for instance).
Change the filter back to -- None --
VS will now crash.
Comment 1 Eric Beisecker 2012-02-28 18:51:25 UTC
This is still and issue with VS 2010 and MfA 4.0.4
Comment 2 Goncalo Oliveira 2012-05-22 06:29:05 UTC
Usually this works right at the first attempt.

1. Open 'Android Device Logging' window
2. Click 'Change Device' and pick one
3. Click 'Toggle Errors'
4. Click 'Clear'

Sometimes it crashes right at step 3.