Roslyn Syntax Visualizser crashes Visual Studio 2019

[vsfeedback]

VSF_TYPE_MARKDOWNIn Visual Studio 2019 (latest and latest preview)

1. Create a new .NET Core console project (.NET Core 3)
2. Open the Syntax Visualizer
3. Click in the sourcecode in program.cs (at the first line of the code) to see the node-graph in the Syntax Visualizer for the entire appliation
4. Right click on the top/root node in the tree-view and choose View Directed Syntax Graph, then the entire Visual Studio crashes

Installed is:

• Visual Studio 2019 (latest updates)
• DGML viewer component
• .NET Compiler Platform SDK
• Workloads (.NET Core, ASP.NET, DESKTOP development)

Expected behavior is that Studio should not crash. Tried on two computers. Also if I just choose a few nodes, it still crashes

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/599151/roslyn-syntax-visualizser-crashes-visual-studio-20.html
VSTS ticketId: 911319
These are the original issue comments:

Roi Chen [MSFT] on 6/10/2019, 04:18 AM (15 days ago):

Thank you for taking the time to log this issue!

I've tried to reproduce and investigate using the description, and attachments already provided. Unfortunately those aren't enough and more information is needed in order to investigate it further.

The easiest way to provide all the information is to use the Visual Studio Feedback Tool. This will ensure that we collect the needed information for you without worrying about what to provide (recording, dump file or ETL trace).

Since this issue is now marked as Need More Info, that workflow is enabled in the Feedback Tool:

• Open Visual Studio Feedback tool.
• Click the banner letting you know that you have problems requesting your attention.
• Click this problem from the list
• Click "View their request and respond" from the problem details banner
• Add a comment, in the Attachments/Record: click Start Recording
• When the Steps Recorder tool appears, perform the steps that reproduce the problem.
• When you're done, choose the Stop Record button.
• Wait a few minutes for Visual Studio to collect and package the information that you recorded.
• Submit. You will be able to see the comment on Developer Community. For security reasons, your files come directly to us and don't appear on Developer Community.

For the full instructions, please see: https://docs.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio-2017?view=vs-2017#when-further-information-is-needed-need-more-info . For information about what data is collected, see https://docs.microsoft.com/en-us/visualstudio/ide/developer-community-privacy?view=vs-2017#data-we-collect

We look forward to hearing from you!

visualstudio on 6/10/2019, 04:54 AM (15 days ago): I will do a try to reproduce it form a blank new Console project in .NET core 3)
Visual Studio Feedback System on 6/25/2019, 03:37 AM (19 hours ago):

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

These are the original issue solutions:
(no solutions)

[jinujoseph]

cc @jmarolf

[sharwell]

Duplicate of #327