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

Excessive memory usage #17317

New Issue
Closed
opened 2026-01-31 05:38:46 +00:00 by claunia · 38 comments
claunia commented 2026-01-31 05:38:46 +00:00
Owner
Copy Link

Originally created by @Masamune3210 on GitHub (Apr 21, 2022).

Windows Terminal version

1.13.10984.0

Windows build number

10.0.22000.0

Other Software

rclone 1.57.0

Steps to reproduce

Run rclone or something else that spews a bunch of things to the terminal, I caused it by having very verbose mode (-vvvv) turned on in rclone while scanning through a mounted cloud drive
Watch as Terminal grows its memory usage until Windows reaps it due to Resource Exhaustion

Expected Behavior

Nominal memory usage, maybe a bit higher than normal

Actual Behavior

image
image

Originally created by @Masamune3210 on GitHub (Apr 21, 2022). ### Windows Terminal version 1.13.10984.0 ### Windows build number 10.0.22000.0 ### Other Software rclone 1.57.0 ### Steps to reproduce Run rclone or something else that spews a bunch of things to the terminal, I caused it by having very verbose mode (-vvvv) turned on in rclone while scanning through a mounted cloud drive Watch as Terminal grows its memory usage until Windows reaps it due to Resource Exhaustion ### Expected Behavior Nominal memory usage, maybe a bit higher than normal ### Actual Behavior ![image](https://user-images.githubusercontent.com/1053504/164485715-c14515a9-6e8c-41d8-89bb-6b39d6cb291a.png) ![image](https://user-images.githubusercontent.com/1053504/164485750-607ebdf6-17c7-4c49-9271-87940f7b8fb8.png)
claunia commented 2026-01-31 05:38:48 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Maybe its a issue with the scroll buffer not getting pruned after a certain amount?
image

@Masamune3210 commented on GitHub (Apr 21, 2022): Maybe its a issue with the scroll buffer not getting pruned after a certain amount? ![image](https://user-images.githubusercontent.com/1053504/164486975-3d71f923-fee0-4eeb-a71e-1ce74ed72c95.png)
claunia commented 2026-01-31 05:38:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

Even if the Terminal had a SHRT_MAX sized buffer, it seems impossible that the memory usage would be in the gigabytes.....

Can you expando that "Terminal Preview" entry in the task manager to see the breakdown of how much memory each child process is using/?

@zadjii-msft commented on GitHub (Apr 21, 2022): Even if the Terminal had a SHRT_MAX sized buffer, it seems impossible that the memory usage would be in the _gigabytes_..... Can you expando that "Terminal Preview" entry in the task manager to see the breakdown of how much memory each child process is using/?
claunia commented 2026-01-31 05:38:48 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

image

@Masamune3210 commented on GitHub (Apr 21, 2022): ![image](https://user-images.githubusercontent.com/1053504/164489165-5a76837c-5c69-4671-a13b-e8796583bc48.png)
claunia commented 2026-01-31 05:38:49 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Also, not sure if Task Manager borked up or if something went wrong but rclone is no longer under the Terminal Preview split, its off floating in its own like a normal process would be instead of as a console app that would normally be under the Terminal

@Masamune3210 commented on GitHub (Apr 21, 2022): Also, not sure if Task Manager borked up or if something went wrong but rclone is no longer under the Terminal Preview split, its off floating in its own like a normal process would be instead of as a console app that would normally be under the Terminal
claunia commented 2026-01-31 05:38:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

... how are there only three processes - yea there should be a shell somewhere under there.

@zadjii-msft commented on GitHub (Apr 21, 2022): ... how are there only three processes - yea there should be a shell somewhere under there.
claunia commented 2026-01-31 05:38:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

Anywho, that doesn't look right. What the heck is leaking?

Can you take a dump of the terminal by right-clicking on the windowsterminal process in Task Manager?

@zadjii-msft commented on GitHub (Apr 21, 2022): Anywho, that doesn't look right. What the heck is leaking? Can you take a dump of the terminal by right-clicking on the `windowsterminal` process in Task Manager?
claunia commented 2026-01-31 05:38:50 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Ok, I have the dump now, its 17.2GB !

@Masamune3210 commented on GitHub (Apr 21, 2022): Ok, I have the dump now, its 17.2GB !
claunia commented 2026-01-31 05:38:50 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

The memory usage isnt going back down, resource reaper will likely kick in soon and kill it
image

@Masamune3210 commented on GitHub (Apr 21, 2022): The memory usage isnt going back down, resource reaper will likely kick in soon and kill it ![image](https://user-images.githubusercontent.com/1053504/164490254-5833bf55-1202-483c-b2d9-3683398dec73.png)
claunia commented 2026-01-31 05:38:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

ah hell well that's maybe problematically large to upload somewhere. NOt even sure that could get uploaded via feedback hub.

Does rclone output like, a LOT of hyperlinks / https:// URLs? I'm trying to mentally figure out what could possibly leak memory like that 😨 Maybe a ton of emoji?

are you running anything like Narrator, Magnifier, any sort of accessibility tool?

@zadjii-msft commented on GitHub (Apr 21, 2022): ah hell well that's maybe problematically large to upload somewhere. NOt even sure that could get uploaded via feedback hub. Does `rclone` output like, a LOT of hyperlinks / `https://` URLs? I'm trying to mentally figure out what could possibly leak memory like that 😨 Maybe a ton of emoji? are you running anything like Narrator, Magnifier, any sort of accessibility tool?
claunia commented 2026-01-31 05:38:51 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

I know its log can contain hyperlinks, usually whenever a hitch or error occurs because it prints the link it was trying to access when very verbose is turned on

@Masamune3210 commented on GitHub (Apr 21, 2022): I know its log can contain hyperlinks, usually whenever a hitch or error occurs because it prints the link it was trying to access when very verbose is turned on
claunia commented 2026-01-31 05:38:51 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

No accessibility features are enabled, no emoji. Would post a pic of the output but its private unfortunately since it deals with cloud syncing and has file names and paths

@Masamune3210 commented on GitHub (Apr 21, 2022): No accessibility features are enabled, no emoji. Would post a pic of the output but its private unfortunately since it deals with cloud syncing and has file names and paths
claunia commented 2026-01-31 05:38:51 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Reaper just ate it, final memory usage was around 18GB

@Masamune3210 commented on GitHub (Apr 21, 2022): Reaper just ate it, final memory usage was around 18GB
claunia commented 2026-01-31 05:38:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

That's fine.

I'm just trying to isolate out the root cause here - in a fresh Terminal window, does gci -recurse (just print out enough text to saturate the buffer) cause the same kind of leak/? Just to try and isolate this to something that is rclone-specific or not

@zadjii-msft commented on GitHub (Apr 21, 2022): That's fine. I'm just trying to isolate out the root cause here - in a fresh Terminal window, does `gci -recurse` (just print out enough text to saturate the buffer) cause the same kind of leak/? Just to try and isolate this to something that is `rclone`-specific or not
claunia commented 2026-01-31 05:38:52 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Memory usage before 62.2MB
Memory usage after 81.7MB

@Masamune3210 commented on GitHub (Apr 21, 2022): Memory usage before 62.2MB Memory usage after 81.7MB
claunia commented 2026-01-31 05:38:52 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Thats after one run of the command

@Masamune3210 commented on GitHub (Apr 21, 2022): Thats after one run of the command
claunia commented 2026-01-31 05:38:52 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

Ran it a few more times, mem usage at 100.5 MB

@Masamune3210 commented on GitHub (Apr 21, 2022): Ran it a few more times, mem usage at 100.5 MB
claunia commented 2026-01-31 05:38:53 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

If you can tell me what to look for in the dump I can try to take a look

@Masamune3210 commented on GitHub (Apr 21, 2022): If you can tell me what to look for in the dump I can try to take a look
claunia commented 2026-01-31 05:38:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

If you can tell me what to look for in the dump I can try to take a look

Honestly, I don't even know what I was gonna look for. Maybe like, way too many threads, or poke around in the TextBuffer to see what that looked like. If there was memory that was accidentally being hung on to by XAML or something, then I'm maybe not the expert in diagnosing where the leak was coming from (from just a dump), bt I might be able to find someone on the XAML team to help take a look.

@zadjii-msft commented on GitHub (Apr 21, 2022): > If you can tell me what to look for in the dump I can try to take a look Honestly, I don't even know what I was gonna look for. Maybe like, way too many threads, or poke around in the TextBuffer to see what that looked like. If there was memory that was accidentally being hung on to by XAML or something, then I'm maybe not the expert in diagnosing where the leak was coming from (from just a dump), bt I might be able to find someone on the XAML team to help take a look.
claunia commented 2026-01-31 05:38:54 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 21, 2022):

17 Threads
Not sure how to look at the TextBuffer unfortunately
If needed I can chunk up the dmp using 7z and upload it somewhere, just might take a while given the file size

@Masamune3210 commented on GitHub (Apr 21, 2022): 17 Threads Not sure how to look at the TextBuffer unfortunately If needed I can chunk up the dmp using 7z and upload it somewhere, just might take a while given the file size
claunia commented 2026-01-31 05:38:54 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 22, 2022):

I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/
This is necessary as allocations won't be tracked with stack traces otherwise.

Would you say that this command should reproduce the issue on my end?

rclone.exe copy ./some/directory ./some_other/directory -vvvv

Is the issue reproducible if you use cmd.exe instead of PowerShell?
Otherwise, if you don't mind, could you post your config file here?

@lhecker commented on GitHub (Apr 22, 2022): I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/ This is necessary as allocations won't be tracked with stack traces otherwise. --- Would you say that this command should reproduce the issue on my end? ``` rclone.exe copy ./some/directory ./some_other/directory -vvvv ``` Is the issue reproducible if you use cmd.exe instead of PowerShell? Otherwise, if you don't mind, could you post your config file here?
claunia commented 2026-01-31 05:38:54 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 22, 2022):

I will set a reminder but likely won't be able to get to it until tomorrow, I am at work currently.

I'm still trying to nail down a cause or at least reproducible path to the bug, but I know it regularly comes up while mounting a Google drive account in rclone in very verbose mode and iterating through the file tree with another program which causes lots of log spew

I will try cmd tomorrow as well and see if I can reproduce anything. If it helps at all, I regularly leave terminal open for multiple days as I hibernate my computer instead of shutting down more often than not

You mean my terminal config file? If so yeah I'll try to post it tonight if I have time or tomorrow if I dont

@Masamune3210 commented on GitHub (Apr 22, 2022): I will set a reminder but likely won't be able to get to it until tomorrow, I am at work currently. I'm still trying to nail down a cause or at least reproducible path to the bug, but I know it regularly comes up while mounting a Google drive account in rclone in very verbose mode and iterating through the file tree with another program which causes lots of log spew I will try cmd tomorrow as well and see if I can reproduce anything. If it helps at all, I regularly leave terminal open for multiple days as I hibernate my computer instead of shutting down more often than not You mean my terminal config file? If so yeah I'll try to post it tonight if I have time or tomorrow if I dont
claunia commented 2026-01-31 05:38:55 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 22, 2022):

I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/ This is necessary as allocations won't be tracked with stack traces otherwise.

Would you say that this command should reproduce the issue on my end?

rclone.exe copy ./some/directory ./some_other/directory -vvvv

Is the issue reproducible if you use cmd.exe instead of PowerShell? Otherwise, if you don't mind, could you post your config file here?

I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/ This is necessary as allocations won't be tracked with stack traces otherwise.

Would you say that this command should reproduce the issue on my end?

rclone.exe copy ./some/directory ./some_other/directory -vvvv

Is the issue reproducible if you use cmd.exe instead of PowerShell? Otherwise, if you don't mind, could you post your config file here?

What process should I enable heap tracing on, the WindowsTerminal.exe?

This is the command I am using

rclone mount "somegoogledriveaccount:" X: -vvvvvvvv --vfs-cache-mode full --cache-dir Z:\rclone --vfs-read-chunk-size 200M --vfs-cache-max-age 30m --vfs-cache-poll-interval 35m --attr-timeout 1h --drive-skip-gdocs --drive-skip-shortcuts --dir-cache-time 5h --transfers 2 --order-by 'size,ascending'

I will try this in a second as the leak is actually happening right now, hibernate maybe involved somehow as I couldn't get it to trigger yesterday after the report, but immediately triggered this morning after resume, but that could be a red herring

settings.zip
Here is my settings.json from Terminal

@Masamune3210 commented on GitHub (Apr 22, 2022): > I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/ This is necessary as allocations won't be tracked with stack traces otherwise. > Would you say that this command should reproduce the issue on my end? > ``` > rclone.exe copy ./some/directory ./some_other/directory -vvvv > ``` > > Is the issue reproducible if you use cmd.exe instead of PowerShell? Otherwise, if you don't mind, could you post your config file here? > I believe debugging a memory leak under Windows is usually done by enabling heap traces with gflags.exe. Here's a tutorial with screenshots I found: https://bugslasher.net/2011/08/09/how-to-troubleshot-native-memory-leaks-on-windows-gflags-and-umdh/ This is necessary as allocations won't be tracked with stack traces otherwise. > > Would you say that this command should reproduce the issue on my end? > > ``` > rclone.exe copy ./some/directory ./some_other/directory -vvvv > ``` > > Is the issue reproducible if you use cmd.exe instead of PowerShell? Otherwise, if you don't mind, could you post your config file here? What process should I enable heap tracing on, the WindowsTerminal.exe? This is the command I am using ``` rclone mount "somegoogledriveaccount:" X: -vvvvvvvv --vfs-cache-mode full --cache-dir Z:\rclone --vfs-read-chunk-size 200M --vfs-cache-max-age 30m --vfs-cache-poll-interval 35m --attr-timeout 1h --drive-skip-gdocs --drive-skip-shortcuts --dir-cache-time 5h --transfers 2 --order-by 'size,ascending' ``` I will try this in a second as the leak is actually happening right now, hibernate maybe involved somehow as I couldn't get it to trigger yesterday after the report, but immediately triggered this morning after resume, but that could be a red herring [settings.zip](https://github.com/microsoft/terminal/files/8541181/settings.zip) Here is my settings.json from Terminal
claunia commented 2026-01-31 05:38:55 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 22, 2022):

What process should I enable heap tracing on, the WindowsTerminal.exe?

Yep, WindowsTerminal.exe!

@lhecker commented on GitHub (Apr 22, 2022): > What process should I enable heap tracing on, the WindowsTerminal.exe? Yep, WindowsTerminal.exe!
claunia commented 2026-01-31 05:38:55 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Apr 22, 2022):

@Masamune3210 using rclone mount with Dropbox there were no huge memory use spikes observed. Did not test against Google Drive or coming out of hibernation.

Here's rclone info:

PS C:\Tools\rclone> .\rclone.exe --version
rclone v1.58.0
- os/version: Microsoft Windows 10 Pro 21H2 (64 bit)
- os/kernel: 10.0.19044.1645 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.17.8
- go/linking: dynamic
- go/tags: cmount

Mount command with --drive-skip-gdocs option remove:

PS C:\Tools\rclone> .\rclone.exe mount remote: X: -vvvvvvvv --vfs-cache-mode full --cache-dir C:\rclone --vfs-read-chunk -size 200M --vfs-cache-max-age 30m --vfs-cache-poll-interval 35m --attr-timeout 1h --drive-skip-shortcuts --dir-cache-time 5h --transfers 2 --order-by 'size,ascending'

And Task Manager sample reading:

rclone_running

@elsaco commented on GitHub (Apr 22, 2022): @Masamune3210 using `rclone mount` with `Dropbox` there were no huge memory use spikes observed. Did not test against `Google Drive` or coming out of hibernation. Here's rclone info: ``` PS C:\Tools\rclone> .\rclone.exe --version rclone v1.58.0 - os/version: Microsoft Windows 10 Pro 21H2 (64 bit) - os/kernel: 10.0.19044.1645 (x86_64) - os/type: windows - os/arch: amd64 - go/version: go1.17.8 - go/linking: dynamic - go/tags: cmount ``` Mount command with `--drive-skip-gdocs` option remove: `PS C:\Tools\rclone> .\rclone.exe mount remote: X: -vvvvvvvv --vfs-cache-mode full --cache-dir C:\rclone --vfs-read-chunk -size 200M --vfs-cache-max-age 30m --vfs-cache-poll-interval 35m --attr-timeout 1h --drive-skip-shortcuts --dir-cache-time 5h --transfers 2 --order-by 'size,ascending'` And `Task Manager` sample reading: ![rclone_running](https://user-images.githubusercontent.com/3933920/164749813-9ad9498e-1829-4cf7-97ec-63748114726d.png)
claunia commented 2026-01-31 05:38:56 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 22, 2022):

Debugging these seldom bugs is always frustrating, I'll see if I can't figure out more over the weekend

@Masamune3210 commented on GitHub (Apr 22, 2022): Debugging these seldom bugs is always frustrating, I'll see if I can't figure out more over the weekend
claunia commented 2026-01-31 05:38:56 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 22, 2022):

What I don't quite understand why your WindowsTerminal.exe process is titled "PowerShell". It should look like this:
image

@lhecker commented on GitHub (Apr 22, 2022): What I don't quite understand why your WindowsTerminal.exe process is titled "PowerShell". It should look like this: ![image](https://user-images.githubusercontent.com/2256941/164769106-53d44393-cb5d-4b12-bbfb-2c857fbf9f8b.png)
claunia commented 2026-01-31 05:38:57 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 22, 2022):

That's what I can't figure out either, and I'm wondering if these two things are somehow related. Somehow something is getting mangled causing something else to go haywire

@Masamune3210 commented on GitHub (Apr 22, 2022): That's what I can't figure out either, and I'm wondering if these two things are somehow related. Somehow something is getting mangled causing something else to go haywire
claunia commented 2026-01-31 05:38:57 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 22, 2022):

You can see in the config file, I'm just using PowerShell, maybe a bug in that particular version? But even then that shouldn't cause Terminal to go haywire like that would it?

@Masamune3210 commented on GitHub (Apr 22, 2022): You can see in the config file, I'm just using PowerShell, maybe a bug in that particular version? But even then that shouldn't cause Terminal to go haywire like that would it?
claunia commented 2026-01-31 05:38:58 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 23, 2022):

Got the weird Task Manager missing process thing again, seems to be related to keeping the Terminal open for a long period. Was fine before I left for work, left my computer on to process some things, when I got home it was like this
image

@Masamune3210 commented on GitHub (Apr 23, 2022): Got the weird Task Manager missing process thing again, seems to be related to keeping the Terminal open for a long period. Was fine before I left for work, left my computer on to process some things, when I got home it was like this ![image](https://user-images.githubusercontent.com/1053504/164885176-89d9f962-727f-431d-b6b8-2f6768c9c266.png)
claunia commented 2026-01-31 05:38:58 +00:00
Author
Owner
Copy Link

@ianjoneill commented on GitHub (Apr 23, 2022):

What I don't quite understand why your WindowsTerminal.exe process is titled "PowerShell". It should look like this: image

I've just opened Terminal Preview 30 times. 8 times I saw "PowerShell", 2 times I saw "Windows Terminal" and the remaining 20 times I saw "WindowsTerminal.exe".

This would maybe suggest it could be a timing thing?

Edit:
It definitely is - if you have task manager open and then start the terminal, the "title" you'll get for the "WindowsTerminal.exe" process will be timing dependant - it could be "PowerShell", "Windows Terminal" or "WindowsTerminal.exe".

If you then close task manager and open it again, the process will have the "PowerShell" title.

Task manager is displaying the window title in place of the process name.

@ianjoneill commented on GitHub (Apr 23, 2022): > What I don't quite understand why your WindowsTerminal.exe process is titled "PowerShell". It should look like this: ![image](https://user-images.githubusercontent.com/2256941/164769106-53d44393-cb5d-4b12-bbfb-2c857fbf9f8b.png) I've just opened Terminal Preview 30 times. 8 times I saw "PowerShell", 2 times I saw "Windows Terminal" and the remaining 20 times I saw "WindowsTerminal.exe". This would maybe suggest it could be a timing thing? Edit: It definitely is - if you have task manager open and then start the terminal, the "title" you'll get for the "WindowsTerminal.exe" process will be timing dependant - it could be "PowerShell", "Windows Terminal" or "WindowsTerminal.exe". If you then close task manager and open it again, the process will have the "PowerShell" title. Task manager is displaying the window title in place of the process name.
claunia commented 2026-01-31 05:38:58 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Apr 23, 2022):

@ianjoneill is the window title same as tab title? With two terminal windows, one elevated and the other one with two tabs, what's shown in the Task Manager is not quiet the same with what tab titles show:

tm_wt_tabs_title

I did use settings early, but there was no Settings tab opened when I took the screenshot. Manually selecting View/Refresh now in Task Manger did not change anything, or restarting Task Manager.

@elsaco commented on GitHub (Apr 23, 2022): @ianjoneill is the window title same as tab title? With two terminal windows, one elevated and the other one with two tabs, what's shown in the Task Manager is not quiet the same with what tab titles show: ![tm_wt_tabs_title](https://user-images.githubusercontent.com/3933920/164915793-14c12e3f-eb0e-4ab2-baf9-7d26ec4670cc.png) I did use settings early, but there was no Settings tab opened when I took the screenshot. Manually selecting `View/Refresh now` in Task Manger did not change anything, or restarting Task Manager.
claunia commented 2026-01-31 05:38:59 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 23, 2022):

Its seemingly just whatever window happens to be open at a certain time, opening a new window will cause the new process to have the correct name of WindowsTerminal.exe, but as far as I can tell nothing will cause the old process to have the correct name again other than sometimes restarting Task Manager which gets it to pick up the new window names

@Masamune3210 commented on GitHub (Apr 23, 2022): Its seemingly just whatever window happens to be open at a certain time, opening a new window will cause the new process to have the correct name of WindowsTerminal.exe, but as far as I can tell nothing will cause the old process to have the correct name again other than sometimes restarting Task Manager which gets it to pick up the new window names
claunia commented 2026-01-31 05:39:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2022):

Yea, FWIW, I've seen the "Terminal has the wrong name sometimes in Task Manager" thing since the earliest days of the Terminal. That's likely just a red herring here. I'm gonna go through and collapse that part of the discussion, since that doesn't seem relevant to the bigger picture "wtf is causing this leak and why can't we repro this" issue.

@zadjii-msft commented on GitHub (Apr 27, 2022): Yea, FWIW, I've seen the "Terminal has the wrong name sometimes in Task Manager" thing since the earliest days of the Terminal. That's likely just a red herring here. I'm gonna go through and collapse that part of the discussion, since that doesn't seem relevant to the bigger picture "wtf is causing this leak and why can't we repro this" issue.
claunia commented 2026-01-31 05:39:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 29, 2022):

Alright, so this is a long shot. Since you seem to be reproducing this consistently, I wonder if you'd help me tell whether the
"segment heap" (Windows' new heap implementation) helps with your outlandish memory usage.

As an Administrator:

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\WindowsTerminal.exe" /v FrontEndHeapDebugOptions /t REG_DWORD /d 8

Restart all instances of Terminal.

If it helps, or even if it doesn't, I am considering enabling this for all Terminal users all the time.

@DHowett commented on GitHub (Apr 29, 2022): Alright, so this is a long shot. Since you seem to be reproducing this consistently, I wonder if you'd help me tell whether the "segment heap" (Windows' new heap implementation) helps with your outlandish memory usage. As an Administrator: ```cmd reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\WindowsTerminal.exe" /v FrontEndHeapDebugOptions /t REG_DWORD /d 8 ``` Restart all instances of Terminal. If it helps, or even if it doesn't, I am considering enabling this for all Terminal users all the time.
claunia commented 2026-01-31 05:39:01 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Apr 29, 2022):

Will test tonight and over the weekend and let you know!

@Masamune3210 commented on GitHub (Apr 29, 2022): Will test tonight and over the weekend and let you know!
claunia commented 2026-01-31 05:39:02 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 6, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (May 6, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:39:02 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (May 10, 2022):

Oops my bad, got busy with real life™ and haven't had a chance to test this yet. I'll try to test soon though

@Masamune3210 commented on GitHub (May 10, 2022): Oops my bad, got busy with real life™ and haven't had a chance to test this yet. I'll try to test soon though
claunia commented 2026-01-31 05:39:03 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (May 15, 2022):

I haven't seen the issue again since I added the new heap style, if I have the issue again I'll be sure to let everybody know

@Masamune3210 commented on GitHub (May 15, 2022): I haven't seen the issue again since I added the new heap style, if I have the issue again I'll be sure to let everybody know
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 Issue-Bug Needs-Attention Needs-Repro Needs-Tag-Fix Needs-Triage Product-Terminal
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#17317
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?