Visual Studio 2015 update 3 crashing after "Getting DataTip text..."

Question

When debugging a C# application in Visual Studio 2015, I am very often getting this message when hovering the mouse over a variable:

After this it freezes and restart, making it impossible to debug.

Anyone have any clue?

Answer 1

Like that thread shared by duDE, please disable the option "Enable property Evaluation and other implicit function calls" under Tools->Options->Debugging->General.

Answer 2

It seems that checking this option:
Tools -> Options -> Debugging -> General: "Use Managed Compatibility Mode".
avoids Visual Studio 2015 from crashing but disables Edit and Continue... which is no good.

So, I am still looking for a better answer.

Sources:

• https://social.msdn.microsoft.com/Forums/vstudio/en-US/8653d0d1-c7ed-4194-8fdc-f183d4ff4ec2/problems-with-debugging-in-vs-2015-when-execution-is-in-a-thread?forum=vsdebug
• https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f3e0c708-0cb4-4e15-9f80-8e713870ebcd/debugging-cant-hover-over-variables-to-see-their-values?forum=visualstudiogeneral
• Datatips (mouse hover over variables in debug mode) not working in Visual Studio 2012 / Win 7 64bit
• Visual Studio 2015 Debugging: Can't expand local variables?
• https://blogs.msdn.microsoft.com/visualstudioalm/2013/10/16/switching-to-managed-compatibility-mode-in-visual-studio-2013/

Quoting the last one:

In Visual Studio 2012, we introduced a new managed debug engine that provides us the ability to more rapidly add new features compared to the older implementation. This can be seen by the number of features introduced in Visual Studio 2013 after only a single year including Managed Return Values, .NET 64-bit Edit and Continue, Async Callstacks Enhancements, and Improved Tasks Window to name a few. Unfortunately, there are still a couple scenarios that are not supported yet with the new debug engine, so in these cases you will have to switch back to the legacy engine.

...so it seems that this is not new.