Current filter:
                                You should refresh the page.
                                  • Approx 90% of the time using Show All References (Shift+F12) causes Visual Studio to crash.  The References screen appears with a progress popup showing it is searching the solution.  It seems to happen more often when I search for public properties that are used across projects.  Searching for a private variable that is used in a single file is more solid but that has crashed on occasion too.

                                    Below is info from the windows event log for the crash.  I do not remember having this problem with the 16.1.6 release.

                                    The description for Event ID 0 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

                                    If the event originated on another computer, the display information had to be saved with the event.

                                    The following information was included with the event:

                                    Error Handler Exception: System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
                                       at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
                                       --- End of inner exception stack trace ---
                                       at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
                                       at System.ServiceModel.Channels.ConnectionStream.EndRead(IAsyncResult asyncResult)
                                       at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
                                       --- End of inner exception stack trace ---
                                       at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult)
                                       at System.ServiceModel.Channels.StreamConnection.EndRead()
                                       --- End of inner exception stack trace ---
                                       at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
                                       at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
                                       at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
                                       at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) \r\n    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
                                       at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
                                       at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
                                       at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)

                                    the message resource is present but the message is not found in the string/message table

                                • Alexander K (DevExpress) 10.07.2016

                                  Hi John,

                                  We are concerned to hear that you faced this issue using our product. Thank you for providing information from the windows event log. We have examined the logs, but it seems that the exception specified there is not related to the Visual Studio crash. This exception is related to connection streams. This functionality is not used when searching for references that cause the Visual Studio crash. It would be a great help for us if you attach to Visual Studio and collect call stacks as described in the following Knowledge Base article: Collecting a call stack to track down the cause of VS crash or freeze issues.

                                  I am looking forward to hearing from you.

                                • John Szentes 10.07.2016

                                  I followed the directions to open a new instance of Visual Studio to debug the 1st instance.  After repeating my steps to duplicate the failure (Shift+F12) the debugging instance popped up an exception dialog  with the following messages
                                    StackOverflowException was unhandled
                                    An unhandled exception of type System.StackOverflowException occurred in DevExpress.CodeAnalysis.VisualBasic.dll

                                  I am not able to get anymore information because the debugging instance of Visual Studio hangs while waiting for the failing instance of Visual Studio to respond
                                      "Microsoft Visual Studio is waiting for a response from ..."

                                • Alexander K (DevExpress) 10.07.2016

                                  Thank you for providing the additional information. We have reproduced this issue on our side. It seems that it is related to grouping elements by a parenting member. As a temporary workaround, I suggest you disable this grouping. We will do our best to solve this issue as soon as possible and inform you of our progress.

                                • John Szentes 10.07.2016

                                  Thank you.  Turning off the grouping does help.

                                • Alexander K (DevExpress) 10.10.2016

                                  You are welcome, John. We are happy to hear that this workaround is helpful.

                                1 Solution

                                Creation Date Importance Sort by

                                Fixed: