Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Right-click opened Terminal window does not release folder handle after navigated away #13793

Closed
ghost opened this issue Aug 20, 2022 · 2 comments
Closed

Right-click opened Terminal window does not release folder handle after navigated away #13793

ghost opened this issue Aug 20, 2022 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@ghost
Copy link

ghost commented Aug 20, 2022

Windows Terminal version

1.14.2281.0

Windows build number

10.0.19044.1889

Other Software

No response

Steps to reproduce

  1. Create a new folder with arbitrary name. E.g. sample.
  2. Using Windows Explorer, navigate into this sample folder. Open a Windows Terminal with right-click context menu.
  3. Close the Windows Explorer window.
  4. Switch back to the Terminal window, navigate away from this folder. E.g. cd ...
  5. Execute rmdir sample within the same Terminal. You should get an error of The process cannot access the file because it is being used by another process..
  6. Close the Terminal window and try to delete that folder again. You should now able to get rid of it without issues.

Expected Behavior

The folder handle should get released once navigated away.

Actual Behavior

Get an error of The process cannot access the file because it is being used by another process..
@ghost ghost added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 20, 2022
@j4james
Copy link
Collaborator

j4james commented Aug 20, 2022

I think this is probably a duplicate of #5506.

@ghost ghost closed this as not planned Won't fix, can't repro, duplicate, stale Aug 20, 2022
@ghost
Copy link
Author

ghost commented Aug 20, 2022

@j4james My bad, will follow that issue instead.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@j4james