[DevExpress Support Team: CLONED FROM T462737: Sequence of steps brings VS2015 down]
Not sure if it's related, but I'm also crashing VS 2015 upon pressing <Tab> on an identifier. Not exactly the same scenario as above, but similar. Too me it feels like VS/CR is getting into a circular loop or stack overflow situation.
Visual Studio crashes on pressing the Tab key on an identifier
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Tor,
We are happy to hear that the issue is resolved now. Please feel free to contact us if you have any further questions.
- v16.2.4Download Official Update
Hi Tor,
Since we are not able to obtain the required information about the issue from the logs in the initial thread, I would ask you to debug this case and manually collect the callstack at the moment when Visual Studio crashes.
Please perform the following steps:
We look forward to hearing from you.
I was able to reproduce the problem. I hit <Tab> on an identifier in a WPF codebehind file. The identifier was an element in the XAML tree. I'm not sure if the scenario was the same the first time I encountered the crash a few days ago.
The exeption is a StackOverflow, see the attached file for more. There were a lot of additional threads, but I don't have time to go through and copy everything so I included the CR threads only in the text file.
Hope this helps,
-Tor
Just had it crash again, this time I hit <Tab> on a method parameter (not a XAML identifier). Unfortunately I was not looking for the crash this time (didn't have a 2nd VS instance open).
Tor, thank you for the provided callstacks.
Please try the following build:
http://downloads.devexpress.com/Share/IDE/161221/DevExpress.CodeRush.Roslyn-16.2.3.16356.vsix
It contains the necessary changes that should fix the issue. Let us know how it works on your side.
I've been using the provided build all day, and no problems so far :)