Bug 38282 - Visual Studio stops responding at each start of a debugging session
Summary: Visual Studio stops responding at each start of a debugging session
Status: RESOLVED DUPLICATE of bug 39433
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-02-01 21:14 UTC by Dimitar Dobrev
Modified: 2016-03-08 03:56 UTC (History)
5 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 DUPLICATE of bug 39433

Description Dimitar Dobrev 2016-02-01 21:14:50 UTC
It had never happened until I upgraded to the latest (as of 1.2.2016) Monodroid.
Comment 1 Dimitar Dobrev 2016-02-01 21:22:46 UTC
I also regularly get:

---------------------------

---------------------------
Exception in OnUnhandledException:

System.NullReferenceException: Object reference not set to an instance of an object.

   at Xamarin.VisualStudio.Debugger.AD7DebugExceptionEvent..ctor(Thread thread, String description) in C:\Users\builder\data\lanes\2696\413372c8\source\XamarinVS\src\Core\VisualStudio\Debugging\MonoTools.Engine\AD7Events.cs:line 433

   at Xamarin.VisualStudio.Debugger.ExceptionsAdapter.OnExceptionThrown(Object sender, TargetEventArgs args) in C:\Users\builder\data\lanes\2696\413372c8\source\XamarinVS\src\Core\VisualStudio\Debugging\MonoTools.Engine\ExceptionsAdapter.cs:line 38
---------------------------
OK   
---------------------------
Comment 2 Dimitar Dobrev 2016-02-02 16:22:16 UTC
After getting this messages I also get:

---------------------------
Microsoft Visual Studio
---------------------------
EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object.

   at Xamarin.VisualStudio.Debugger.AD7DebugExceptionEvent..ctor(Thread thread, String description) in C:\Users\builder\data\lanes\2696\413372c8\source\XamarinVS\src\Core\VisualStudio\Debugging\MonoTools.Engine\AD7Events.cs:line 433

   at Xamarin.VisualStudio.Debugger.ExceptionsAdapter.OnExceptionThrown(Object sender, TargetEventArgs args) in C:\Users\builder\data\lanes\2696\413372c8\source\XamarinVS\src\Core\VisualStudio\Debugging\MonoTools.Engine\ExceptionsAdapter.cs:line 42

   at Mono.Debugging.Client.DebuggerSession.OnTargetEvent(TargetEventArgs args)

   at Mono.Debugging.Soft.SoftDebuggerSession.HandleBreakEventSet(Event[] es, Boolean dequeuing)

   at Mono.Debugging.Soft.SoftDebuggerSession.HandleEventSet(EventSet es)

   at Mono.Debugging.Soft.SoftDebuggerSession.EventHandler()
---------------------------
OK   
---------------------------
Comment 3 Dimitar Dobrev 2016-02-02 18:36:23 UTC
I started getting this every time, could you at least comment or do I have to downgrade to Xamarin 3 again? It's been reported nearly a week ago at https://stackoverflow.com/questions/35011940/xamarin-strange-exception-in-vs2015.
Comment 4 Dimitar Dobrev 2016-02-02 21:09:01 UTC
I have downgraded to Xamarin 3 again. I waited for two months until you fix a regression as critical as https://bugzilla.xamarin.com/show_bug.cgi?id=36250 just so I can get this.
I've been at an increasing difficulty to express my disappointment with you. The main reason is that I have followed you and used your software since 2009 and therefore I know you can do better than this. There will always be bugs etc. but I really hope something like this would start happening more and more rarely until it does as often as it did just a few years ago.
Comment 5 Dimitar Dobrev 2016-02-24 15:23:21 UTC
I still get these null refs, when it happens, I am forced to restart VS to stop them - for a while, and then they appear again. When are you going to fix this?
Comment 6 João Matos 2016-03-03 13:24:57 UTC
Please attach a reproduction so we can take a look at this, thanks!
Comment 7 Brendan Zagaeski (Xamarin Team, assistant) 2016-03-08 03:56:47 UTC
I will mark this as a duplicate of a new bug I have filed to gather all of the information reported by various customers for this issue so far.

*** This bug has been marked as a duplicate of bug 39433 ***