-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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.
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
WT doesn't close process handles to openconsole.exe #8706
Comments
How do you keep finding these things? Do you just routinely check out the handles for all the stuff you run on your machine? I'm not complaining, but it is strange 😉 |
I'm generally concerned with performance, especially that of apps which have captured my fancy in some way. And I have several tools (some my own) for observing performance (and I enjoy using them). In this case, I was trying to find differences between instances of WT which use little CPU when idling and ones which use a lot of CPU when idling (see #8625). |
It rather raises the question as to how we missed this. Closes #8706
🎉This issue was addressed in #8707, which has now been successfully released as Handy links: |
🎉This issue was addressed in #8707, which has now been successfully released as Handy links: |
…8707) It rather raises the question as to how we missed this. Closes microsoft#8706
Environment
Microsoft Windows 10 Pro for Workstations
10.0.19042.685 (2009, 20H2)
WindowsTerminalPreview_1.5.3242.0_x64
Release version does it too.
Steps to reproduce
Monitor WT's open "Process" handles while opening/closong new tabs or panes.
Expected behavior
WT will close its newly acquired handle to OpenConsole.exe
Actual behavior
WT does not close the handle
Using HANDLE64.EXE (Sysinternals, could also use their ProcessExplorer) ...
The text was updated successfully, but these errors were encountered: