Visual Studio 2015 Update 3 crashes after "Retrieving Text DataTip ..."

Question

When debugging a C # application in Visual Studio 2015, I very often get this message when I hover over a variable:

After that, it freezes and restarts, which makes debugging impossible.

Does anyone have a key?

Answer 1

It seems like checking this parameter:
Tools → Options → Debugging → General: “Use compatible compatibility mode” .
avoids the error in Visual Studio 2015, but disables Modify and continue ... which is not good.

So I'm 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 (hovering over variables in debug mode) that do not work in Visual Studio 2012 / Win 7 64bit
• Visual Studio 2015 debugging: unable to expand local variables?
• https://blogs.msdn.microsoft.com/visualstudioalm/2013/10/16/switching-to-managed-compatibility-mode-in-visual-studio-2013/

Quoting the latter:

In Visual Studio 2012, we introduced a new managed debugging engine that gives us the ability to add new features faster than the old version. This can be seen by the number of features introduced in Visual Studio 2013 in just one 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 several scenarios that are not yet supported by the new debugging mechanism, so in these cases you will have to switch back to the outdated engine.

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

Answer 2

Like this thread, used in conjunction with duDE, disable the "Enable property evaluation and other implicit function calls" option in Tools-> Options → Debugging-> General.

Answer 3

This problem should be fixed in Visual Studio "15" Preview 5 (available here . Unfortunately, there are no known workarounds other than those already mentioned for updating Visual Studio 2015 3.