You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue occur when all extensions are disabled?: Yes
VS Code Version:1.100.0-insider (c90ebc27218affc8231b0acf4fd4e6856499dd2f, 2025-04-25T05:04:04.259Z)
OS Version: Windows 11 Pro Insider Preview, Version 24H2 (OS Build 26200.5562) (Reported as Windows_NT x64 10.0.26200 by VS Code)
Steps to Reproduce:
Create a new file or open an existing file with the .ini extension.
Paste the specific text content provided in the "Additional Context" section below into the editor. (Alternatively, paste the text into a new untitled file; VS Code Insiders automatically detects it as INI language mode).
Ensure the language mode is set to INI.
Place the cursor at the very beginning of the file (position 0, before the first character).
Press the Enter key twice to insert two new lines.
Expected Behavior:
Two new lines should be inserted at the beginning of the file without any freezing or performance issues in the VS Code window.
Actual Behavior:
The entire VS Code window becomes unresponsive immediately after pressing Enter the second time (Step 5). The window stops responding to any clicks or keyboard input. Eventually, a dialog appears with the title "Visual Studio Code - Insiders" and the main instruction "The window is not responding", offering options to "Reopen", "Close", or "Keep Waiting". (See screenshot below)
Additional Context:
This issue only occurs when the file's language mode is detected or set as INI. If I manually change the language mode to Plain Text, or if the file has a different extension like .txt or .md (causing a different language mode to be active), the issue does not occur with the same text content and steps.
The issue reproduces consistently even when launching VS Code Insiders with code-insiders --disable-extensions or using a temporary clean profile (code-insiders --user-data-dir <temp_folder> --extensions-dir <temp_folder2>).
I also confirmed this via the "Help: Start Extension Bisect" command, where the problem occurred in the first step with many extensions disabled.
This issue does not reproduce in the current Stable version of VS Code (tested with both my regular profile and a clean profile) using the exact same steps and text content. This strongly suggests an issue specific to the Insiders build.
The Windows display language and system locale are set to Japanese (日本語). I mention this in case it might be relevant.
The specific text content (Japanese text included) that triggers the freeze is provided below:
Click to expand the text content causing the freeze
Does this issue occur when all extensions are disabled?: Yes
1.100.0-insider
(c90ebc27218affc8231b0acf4fd4e6856499dd2f
,2025-04-25T05:04:04.259Z
)Steps to Reproduce:
.ini
extension.INI
language mode).INI
.Enter
key twice to insert two new lines.Expected Behavior:
Two new lines should be inserted at the beginning of the file without any freezing or performance issues in the VS Code window.
Actual Behavior:
The entire VS Code window becomes unresponsive immediately after pressing Enter the second time (Step 5). The window stops responding to any clicks or keyboard input. Eventually, a dialog appears with the title "Visual Studio Code - Insiders" and the main instruction "The window is not responding", offering options to "Reopen", "Close", or "Keep Waiting". (See screenshot below)
Additional Context:
INI
. If I manually change the language mode toPlain Text
, or if the file has a different extension like.txt
or.md
(causing a different language mode to be active), the issue does not occur with the same text content and steps.code-insiders --disable-extensions
or using a temporary clean profile (code-insiders --user-data-dir <temp_folder> --extensions-dir <temp_folder2>
).日本語
). I mention this in case it might be relevant.Click to expand the text content causing the freeze
The text was updated successfully, but these errors were encountered: