Integrated terminal fails to recover to previous state when vscode is closed

[Rowlando13]

Type: Bug

I normally run 5 terminals open at the same same time. They are as follows: to run npm, to run vagrant, to commit into one repo, to commit into another repo, and a working one. I always have these open. They are the first thing I open and I never close them. I if I need another, then I open another terminal window. The bug is that when I open vs code there is only terminal open, seemly a random one of the five I noramaly have. The bug is intermittent. It happens most commonly when I my linux system crashes but not always. It also occurs when I shut down the system normally.

VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:35:30.018Z) OS version: Linux x64 5.15.0-60-generic snap Modes: Sandboxed: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-10400H CPU @ 2.60GHz (8 x 1426)| |GPU Status|2d_canvas: unavailable_software
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off| |Load (avg)|1, 1, 0| |Memory (System)|31.13GB (25.80GB free)| |Process Argv|--no-sandbox --force-user-env --unity-launch| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|ubuntu| |XDG_CURRENT_DESKTOP|Unity| |XDG_SESSION_DESKTOP|ubuntu| |XDG_SESSION_TYPE|x11|

Extensions (24)

Extension|Author (truncated)|Version ---|---|--- vscode-intelephense-client|bme|1.9.5 better-toml|bun|0.3.2 path-intellisense|chr|2.8.4 gc-excelviewer|Gra|4.2.56 vscode-graphviz|joa|0.0.6 rainbow-csv|mec|3.5.0 php-namespace-resolver|Meh|1.1.9 vscode-docker|ms-|1.23.3 isort|ms-|2022.8.0 python|ms-|2023.2.0 jupyter|ms-|2023.1.2010391206 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.14 vscode-jupyter-cell-tags|ms-|0.1.6 vscode-jupyter-slideshow|ms-|0.1.5 remote-containers|ms-|0.275.1 remote-ssh|ms-|0.96.0 remote-ssh-edit|ms-|0.84.0 remote-explorer|ms-|0.2.0 php-docblocker|nei|2.7.0 vscode-yaml|red|1.11.0 bash-debug|rog|0.3.9 code-spell-checker|str|2.16.0 php-debug|xde|1.31.1

[Rowlando13]

[Rowlando13]

Since this is intermittent, I assume you will need logs of some sort. I am happy to support.

[meganrogge]

Thanks, yeah will be hard to reproduce.

The logs are found in the Pty Host output channel with log level set to trace

[Rowlando13]

Can you be a little more specific? I don't know what the PTY Host output channel is and how to set it to trace?

[meganrogge]

In the Output view, select Pty Host

In the command palette, run this command and select Trace

[Rowlando13]

Thank you for the detailed instructions. I was able to set my developer log level to trace, but was not able to see the pty host output channel. I just have normal vs code. Is it an extension? because on my sidebar, I have explorer and search but no pty host. I also did some googling but could not find anything.

[meganrogge]

This command and then there will be a dropdown

[Rowlando13]

Got it. So do you want for me to wait for it to happen again and then send you the logs? ptyhost.log file only has a day or so of logs. I have not had the issue in that time. It usually happens once a week or so.

[meganrogge]

Yes, when it next happens, the logs would be great

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[Rowlando13]

Keeping this issue open would be great. It happen across to 2 OS's ubuntu 20.02 and 22.04. I have been watching but it has not happened yet/

[Rowlando13]

So it finally happened again @meganrogge . Here is the last bit of the ptyhost.log. This is the only obvious snippet that appeared. If you need more, please let me know.

[Rowlando13]

2023-03-19 14:41:21.348 [warning] Couldn't get layout info, a terminal was probably disconnected Could not find pty on pty host 2023-03-19 14:41:21.349 [warning] Couldn't get layout info, a terminal was probably disconnected Could not find pty on pty host 2023-03-19 14:41:21.349 [warning] Couldn't get layout info, a terminal was probably disconnected Could not find pty on pty host 2023-03-19 14:41:26.045 [warning] Persistent process "1": Process had no disconnect runners but was an orphan 2023-03-19 14:41:26.045 [info] Persistent process reconnection "1" 2023-03-19 14:41:26.048 [warning] Persistent process "2": Process had no disconnect runners but was an orphan 2023-03-19 14:41:26.048 [info] Persistent process reconnection "2" 2023-03-19 14:41:26.130 [info] Persistent process "1": Replaying 2672 chars and 1 size events 2023-03-19 14:41:26.188 [info] Persistent process "2": Replaying 5847 chars and 1 size events

[Rowlando13]

Happened again today: 2023-03-21 14:11:58.789 [warning] Persistent process "1": Process had no disconnect runners but was an orphan 2023-03-21 14:11:58.789 [info] Persistent process reconnection "1" 2023-03-21 14:11:58.808 [info] Persistent process "1": Replaying 2621 chars and 1 size events

[Rowlando13]

Happened again. Appeared to recover 4 terminals but 1 was frozen. 2023-03-22 14:19:28.599 [warning] Couldn't get layout info, a terminal was probably disconnected Could not find pty on pty host 2023-03-22 14:19:32.719 [warning] Persistent process "3": Process had no disconnect runners but was an orphan 2023-03-22 14:19:32.720 [info] Persistent process reconnection "3" 2023-03-22 14:19:32.748 [info] Persistent process "3": Replaying 5243 chars and 1 size events 2023-03-22 14:19:32.777 [warning] Persistent process "3": Process had no disconnect runners but was an orphan 2023-03-22 14:19:32.777 [info] Persistent process reconnection "3" 2023-03-22 14:19:32.783 [info] Persistent process "3": Replaying 5243 chars and 1 size events 2023-03-22 14:19:36.718 [warning] Persistent process "2": Process had no disconnect runners but was an orphan 2023-03-22 14:19:36.719 [info] Persistent process reconnection "2" 2023-03-22 14:19:36.719 [warning] Persistent process "1": Process had no disconnect runners but was an orphan 2023-03-22 14:19:36.720 [info] Persistent process reconnection "1" 2023-03-22 14:19:36.738 [info] Persistent process "2": Replaying 2689 chars and 1 size events 2023-03-22 14:19:36.742 [info] Persistent process "1": Replaying 2878 chars and 1 size events

[meganrogge]

@Rowlando13 are you still encountering this? a lot of fixes have happened since last spring.

[Rowlando13]

I have not encountered the problem in several months.

[meganrogge]

Let us know if you see it again.