starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

OpenConsole/WindowsTerminal keep handles on directory after closing tab, when terminal is opened through context menu. #16130

New Issue
Closed
opened 2026-01-31 04:58:21 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:58:21 +00:00
Owner
Copy Link

Originally created by @JornVernee on GitHub (Dec 15, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

  1. Create a test directory, e.g. test
  2. Open the directory in Windows explorer,
  3. Use the right-click context menu to "Open in Windows terminal". This should open a powershell instance with the working directory set to the test directory. (Note that opening the terminal somewhere else, and cd'ing to the test directory will not create the problematic file handles).
  4. Open a new Windows Terminal tab (e.g. I'm using Ubuntu to test). Make sure that this shell is not using the test directory as a working directory.
  5. Close the original (powershell) tab that has the test directory as working directory.
  6. Try to delete the test directory. This should fail because the directory is still in use by another process.

At this point, you could use e.g. Resource Monitor to see that OpenConsole.exe and WindowsTerminal.exe still have open handles on the test directory.
image

The workaround for this is to close the Windows terminal instance, which will release the handles.

Expected Behavior

After closing the original tab in Windows terminal, it should be possible to delete the test directory.

This feels like a resource leak, since I am no longer using the test directory through Windows Terminal, and (AFAIK) there is nothing I can do in Windows Terminal to release those file handles.

Actual Behavior

Deleting the test directory failes, because there are still open handles on it.

Originally created by @JornVernee on GitHub (Dec 15, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce 1. Create a test directory, e.g. `test` 2. Open the directory in Windows `explorer`, 3. Use the right-click context menu to "Open in Windows terminal". This should open a powershell instance with the working directory set to the `test` directory. (Note that opening the terminal somewhere else, and `cd`'ing to the `test` directory will not create the problematic file handles). 4. Open a new Windows Terminal tab (e.g. I'm using Ubuntu to test). Make sure that this shell is not using the `test` directory as a working directory. 5. Close the original (powershell) tab that has the `test` directory as working directory. 6. Try to delete the `test` directory. This should fail because the directory is still in use by another process. At this point, you could use e.g. Resource Monitor to see that OpenConsole.exe and WindowsTerminal.exe still have open handles on the test directory. ![image](https://user-images.githubusercontent.com/5962029/146224510-d96d0039-0eaa-4469-a5b4-b3fa2611465f.png) The workaround for this is to close the Windows terminal instance, which will release the handles. ### Expected Behavior After closing the original tab in Windows terminal, it should be possible to delete the `test` directory. This feels like a resource leak, since I am no longer using the `test` directory through Windows Terminal, and (AFAIK) there is nothing I can do in Windows Terminal to release those file handles. ### Actual Behavior Deleting the `test` directory failes, because there are still open handles on it.
claunia added the Resolution-Duplicate label 2026-01-31 04:58:21 +00:00
claunia commented 2026-01-31 04:58:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 15, 2021):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #5506 for more discussion.

/dup #5506

@zadjii-msft commented on GitHub (Dec 15, 2021): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #5506 for more discussion. /dup #5506
claunia commented 2026-01-31 04:58:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 15, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 15, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 04:58:22 +00:00
Author
Owner
Copy Link

@JornVernee commented on GitHub (Dec 15, 2021):

Thanks! I couldn't find it when searching.

@JornVernee commented on GitHub (Dec 15, 2021): Thanks! I couldn't find it when searching.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16130
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?