Current filter:
                                You should refresh the page.
                                  • [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.

                                • Alex B.G. (DevExpress) 12.20.2016

                                  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:

                                  1. Run the first Visual Studio Instance. Open the problematic source code.
                                  2. Run the second instance of Visual Studio and attach it to the first one (for more information please see the following article: Collecting a call stack to track down the cause of VS crash or freeze issues).
                                  3. Switch to the first instance and try to reproduce the issue.
                                  4. Then the second instance will recognize a crash, copy the exception details to a text file and send it to us.
                                  5. Pressing F5 key, collect all exception details to a text file until the first instance of Visual Studio shuts down.
                                  We look forward to hearing from you.
                                • Tor Langlo 12.20.2016

                                  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 Langlo 12.20.2016

                                  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).

                                • Alex B.G. (DevExpress) 12.21.2016

                                  Tor, thank you for the provided callstacks.

                                  Please try the following build:

                                  It contains the necessary changes that should fix the issue. Let us know how it works on your side.

                                • Tor Langlo 12.21.2016

                                  I've been using the provided build all day, and no problems so far :)

                                1 Solution

                                Creation Date Importance Sort by


                                Additional information:

                                We are happy to hear that the issue is resolved now. Please feel free to contact us if you have any further questions.