No text in new terminal (or any other terminal)

[alexr00]

I noticed that all my terminal text had vanished. I created a new terminal, and even in the new terminal there was no text:

I don't see any relevant errors in the console.

[alexr00]

Interestingly, this seems to have happened across all three windows I have open.

[BMourguesFieldbox]

I feel there are missing information in your issue :
https://github.com/microsoft/vscode/blob/main/CONTRIBUTING.md#writing-good-bug-reports-and-feature-requests

[sarahjeeeze]

I have the same issue - i just installed update 1.99.1, OS is windows 11

[anthonykim1]

@alexr00 which shell are you using on which os?
does it help if you turn off terminal shell integration setting?

[alexr00]

I haven't seen the issue again, so I can't comment on whether turning off shell integration helps.

This is pwsh on Windows.

[meganrogge]

if anyone can reproduce, can you share your settings.json file and also do a trace log while creating a terminal? https://github.com/microsoft/vscode/wiki/Terminal-Issues#enabling-trace-logging
/label info-needed terminal

[alxdrl]

Similar issue here: terminal blacks out & freeze when resized

Context:

• i7-8665U / 16GB
• Windows 11 23H2 Build 22631.5189
• PowerShell 7.4.7
• oh-my-posh version 23.20.3
• VSCode 1.99.3
• default terminal set to pwsh

Repro

1. new vscode window
2. open a terminal (Shift+Ctrl+`)
3. do nothing
4. open explorer pane (Shift+Ctrl+E)
5. hide pane (Ctrl+B)

=> terminal went black at step 4 does not come back, must kill the terminal

Logs

settings.json : { "terminal.integrated.gpuAcceleration": "off" }

ptyhost trace log ptyhost.txt

2025-04-18 09:05:52.633 [trace] TerminalProcess#shutdown 
    at Os.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:33:9123)
    at au.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:47:11711)
    at M.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:47:2687)
    at R.i.<computed> (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:46:2962)
    at Object.call (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:28:4204)
    at Gr.s (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:81166)
    at Gr.q (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:80689)
    at pi.value (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:80091)
    at E.B (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2373)
    at E.C (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2443)
    at E.fire (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2660)
    at MessagePortMain.C (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:24:29879)
    at MessagePortMain.emit (node:events:518:28)
    at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2949)
2025-04-18 09:05:52.634 [trace] TerminalProcess#_queueProcessExit 
    at Os.X (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:33:8060)
    at Os.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:33:9214)
    at au.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:47:11711)
    at M.shutdown (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:47:2687)
    at R.i.<computed> (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:46:2962)
    at Object.call (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:28:4204)
    at Gr.s (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:81166)
    at Gr.q (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:80689)
    at pi.value (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:80091)
    at E.B (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2373)
    at E.C (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2443)
    at E.fire (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:26:2660)
    at MessagePortMain.C (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:24:29879)
    at MessagePortMain.emit (node:events:518:28)
    at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2949)
2025-04-18 09:05:52.634 [trace] [RPC Response] PtyService#shutdown undefined
2025-04-18 09:05:52.893 [trace] node-pty.IPty#kill
2025-04-18 09:05:53.001 [trace] [RPC Event] PtyService#_onProcessExit.fire({"id":1,"event":0})
2025-04-18 09:05:53.053 [trace] TerminalProcess#_queueProcessExit 
    at Os.X (file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:33:8060)
    at file:///c:/Users/xxxxxxxx/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/platform/terminal/node/ptyHostMain.js:33:7850
    at EventEmitter2.fire (c:\Users\xxxxxxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules\node-pty\lib\eventEmitter2.js:41:22)
    at Socket.<anonymous> (c:\Users\xxxxxxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules\node-pty\lib\terminal.js:93:76)
    at Socket.emit (node:events:518:28)
    at Terminal.emit (c:\Users\xxxxxxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules\node-pty\lib\terminal.js:155:34)
    at Socket.<anonymous> (c:\Users\xxxxxxxx\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules\node-pty\lib\windowsTerminal.js:100:23)
    at Socket.emit (node:events:518:28)
    at Pipe.<anonymous> (node:net:343:12)

Anti-repro

1. new vscode window
2. open a terminal (Shift+Ctrl+`)
3. type a few command to fill ~75% of vertical space in terminal window
4. open explorer pane (Shift+Ctrl+E)
5. hide pane (Ctrl+B)

=> everything's fine

Hope this helps.

[meganrogge]

does this change it terminal.integrated.windowsUseConptyDll?

[alxdrl]

Yes it does. The integrated terminal stays alive when terminal.integrated.windowsUseConptyDll is set to true and trying the repro scenario.

[meganrogge]

is there a reason you changed that to false ?