-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
C# file with very long line freeze editor #163434
Labels
bug
Issue identified by VS Code Team member as probable bug
grammar
Syntax highlighting grammar
insiders-released
Patch has been released in VS Code Insiders
verified
Verification succeeded
Milestone
Comments
Here is a reduced repro:
By using the
which comes from here @vcsjones As a workaround, you can reduce the limit for C# files from 20k to something smaller e.g.:
@alexr00 We also have the option of reducing C#'s default. We already did that for javascript to 2500. |
alexr00
added a commit
that referenced
this issue
Nov 22, 2022
alexr00
added a commit
that referenced
this issue
Nov 22, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Issue identified by VS Code Team member as probable bug
grammar
Syntax highlighting grammar
insiders-released
Patch has been released in VS Code Insiders
verified
Verification succeeded
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Download this file: https://raw.githubusercontent.com/dotnet/runtime/20d229ca0c4f6655d3a26caff9a2896dbe08bfb9/src/libraries/System.IO.Hashing/tests/XxHash3Tests.cs
Make sure it has a
.cs
extension.Close all current instances of VS Code
Open it with VS Code with all extensions disabled:
code --disable-extensions ~/Downloads/XxHash3Tests.cs
Scroll around. In a few seconds the editor will lock up.
This file has some extremely long lines, around ~65,000. I was under the impression though that VS Code stopped rendering at some cutoff, however.
It appears the issue is the syntax highlighting for C#. If I open it as plain text, then I can no longer reproduce the behavior.
The text was updated successfully, but these errors were encountered: