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
All state is cleared from the project. Terminal ptys released, extensions unloaded, etc.
Actual
"Session" is still running:
Notes
It used to be that state was lost on close, so the current behavior is orders of magnitude more usable. I think I am seeing a strangeness related to PR #2723. Code server is a bit different from VS Code in that there is a difference between the window being closed, and the folder is closed. Since it's a server it could be the browser crashed. Would it be possible to tease those apart? That being said, if that is too invasive I can live with needing to close the shell manually vs having my terminal lost when Amtrak's wifi flakes out. =)
This issue can be reproduced in VS Code: No
The text was updated successfully, but these errors were encountered:
Ahhhh yeah when we close the folder it makes sense to me that we should
close the associated terminal sessions.
When we get the close request we should hit up the terminal provider and
ask it to close its sessions for the workspace/folder that was just
closed.
OS/Web Information
Steps to Reproduce
Expected
All state is cleared from the project. Terminal ptys released, extensions unloaded, etc.
Actual
"Session" is still running:

Notes
It used to be that state was lost on close, so the current behavior is orders of magnitude more usable. I think I am seeing a strangeness related to PR #2723. Code server is a bit different from VS Code in that there is a difference between the window being closed, and the folder is closed. Since it's a server it could be the browser crashed. Would it be possible to tease those apart? That being said, if that is too invasive I can live with needing to close the shell manually vs having my terminal lost when Amtrak's wifi flakes out. =)
This issue can be reproduced in VS Code: No
The text was updated successfully, but these errors were encountered: