The Wayback Machine - https://web.archive.org/web/20211207221108/https://github.com/dotnet/aspnetcore/issues/38877
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Compiler crashing issues reported through internal telemetry #38877

Open
mkArtakMSFT opened this issue Dec 7, 2021 · 1 comment
Open

Compiler crashing issues reported through internal telemetry #38877

mkArtakMSFT opened this issue Dec 7, 2021 · 1 comment
Labels
area-razor.compiler bug Priority:1 razor.compiler-toolingsupport
Milestone
.NET 7 Planning

Comments

@mkArtakMSFT
Copy link
Contributor

@mkArtakMSFT mkArtakMSFT commented Dec 7, 2021

Internal Error - System.ArgumentException: startCommentStar at Microsoft.AspNetCore.Razor.Language.Syntax.InternalSyntax.SyntaxFactory.RazorCommentBlock(SyntaxToken startCommentTransition, SyntaxToken startCommentStar, SyntaxToken comment, SyntaxToken endCommentStar, SyntaxToken endCommentTransition) at --- This actually looks like a compiler error @Artak Mkrtchyan could you file a separate issue to track? You should be able to use PRISM to better understand users who ran into this (Btw old editor would have killed VS in this scenario, new editor the experience falls over instead 😃)

More context: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1435565
@mkArtakMSFT mkArtakMSFT added this to the .NET 7 Planning milestone Dec 7, 2021
@msftbot
Copy link
Contributor

@msftbot msftbot bot commented Dec 7, 2021

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-razor.compiler bug Priority:1 razor.compiler-toolingsupport
Projects
None yet
Milestone
.NET 7 Planning
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@mkArtakMSFT