Large files fail to open with a blank editor — large-file confirmation pane crashes during DI instantiation ($di$dependencies undefined)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to 3.6.31, opening any text file larger than the workbench.editorLargeFileConfirmation threshold results in a completely blank editor pane. No “this file is large, open anyway?” confirmation/notice is shown, and the file never renders. CPU usage does not spike — the editor is not frozen or busy; it silently gives up.
This affects all plain-text file types equally (.log, .json, .txt, etc.), so it is not extension-specific and not tied to any one file format.
The Developer Tools console shows that the editor correctly detects the file as large and tries to display the large-file notice pane instead of the text editor — but instantiating that notice pane throws during dependency injection, so nothing is rendered.
Key console errors (Windows, 3.6.31):

ERR Error: The file is not displayed in the text editor because it is very large (41.53MB).
    at QYn (workbench.desktop.main.js:64:738)
    at NMs.handleSetInputError (...)
    at NMs.setInput (...)
    at async kHd.doSetInput (...)
    at async kHd.doOpenEditor (...)
    at async kHd.openEditor (...)

ERR Cannot read properties of undefined (reading '$di$dependencies'): TypeError: Cannot read properties of undefined (reading '$di$dependencies')
    at Object.e [as getServiceDependencies] (workbench.desktop.main.js:61:62772)
    at Xfg._createInstance (workbench.desktop.main.js:47926:1595)
    at Xfg.createInstance (workbench.desktop.main.js:47926:1522)
    at v$i.instantiate (workbench.desktop.main.js:36596:79953)
    at kHd.doInstantiateEditorPane (workbench.desktop.main.js:36612:66136)
    at kHd.doCreateEditorPane (...)
    at kHd.doShowEditorPane (...)
    at kHd.doOpenEditor (...)
    at kHd.doShowError (...)
    at kHd.openEditor (...)

The sequence is: doShowError → tries to show the large-file pane → doInstantiateEditorPane → createInstance → getServiceDependencies reads $di$dependencies on an undefined target → throws. Because the error pane itself fails to instantiate, the editor area is left blank.

Steps to Reproduce

  1. Set “workbench.editorLargeFileConfirmation” to a value smaller than your test file (e.g. 10).
  2. Open any plain-text file larger than that threshold (tested with a ~37–41MB .log file).
  3. Observe: no confirmation prompt appears, and the editor pane is blank. CPU stays idle.
  4. Open Developer Tools → Console to see the $di$dependencies TypeError above.

Reproduces with all extensions disabled (Disable All Installed Extensions + reload), so this is not extension-related.

Expected Behavior

The editor should either:

  • show the large-file confirmation/notice (“File is large — open anyway?”), as it did before the update, or
  • open the file normally if confirmation is disabled.

It should not leave a blank editor pane with an uncaught DI exception.

Screenshots / Screen Recordings

cb.png
cb.png882×734 36 KB

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

Additional Information

  • This was working correctly before updating to the 3.6.x line — large files used to prompt a confirmation before opening.
  • workbench.editorLargeFileConfirmation is set to 10 (verified in User settings; settings.json has no syntax errors).
  • The error originates in workbench.desktop.main.js (the bundled app), not in any extension, which points to a regression in the bundled editor-pane / DI registration rather than a user-side configuration issue.
  • Workaround that avoids the broken path: raise workbench.editorLargeFileConfirmation above the file size (or set to 0) so the large-file notice pane is never instantiated; the file then opens in the normal text editor. Alternatively, “Open With… → Text Editor” can bypass it.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report. The stack trace and repro steps really helped. I can see the console screenshot showing a $di$dependencies TypeError when it tries to show the large-file pane.

This is a known regression in 3.6.31. The large-file confirmation pane crashes during instantiation, so the editor area stays blank. We’ve identified the issue and the fix is ready, but it didn’t make it into the 3.6.31 build. It should land in the next stable release.

Your workaround is correct and you can use it until you update:

  • raise workbench.editorLargeFileConfirmation above the file size, or set it to 0
  • or open it via Open With… → Text Editor

Once the new version is out, I’ll follow up in the thread. Let me know if anything else comes up.