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

is this a memory leak? #17646

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

Originally created by @lost22git on GitHub (Jun 6, 2022).

Windows Terminal version

1.13.22053001

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

image

Even if I close wt , the process still exists and the memory usage doesn't drop

Expected Behavior

No response

Actual Behavior

image

Originally created by @lost22git on GitHub (Jun 6, 2022). ### Windows Terminal version 1.13.22053001 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce ![image](https://user-images.githubusercontent.com/65008815/172135890-ab0ea5de-4a86-4132-9c55-c6154075a8ed.png) ### Even if I close `wt` , the process still exists and the memory usage doesn't drop ### Expected Behavior _No response_ ### Actual Behavior ![image](https://user-images.githubusercontent.com/65008815/172136362-f68a320a-c137-49b7-884f-960e5f3bf0a1.png)
claunia commented 2026-01-31 05:48:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 6, 2022):

That sure looks like a memory leak to me. What were you doing at the time this occurred? Is it reproducible for you/?

@zadjii-msft commented on GitHub (Jun 6, 2022): That sure looks like a memory leak to me. What were you doing at the time this occurred? Is it reproducible for you/?
claunia commented 2026-01-31 05:48:50 +00:00
Author
Owner
Copy Link

@lost22git commented on GitHub (Jun 6, 2022):

I don't know how to reproduce the problem, so only continue to observe

@lost22git commented on GitHub (Jun 6, 2022): I don't know how to reproduce the problem, so only continue to observe
claunia commented 2026-01-31 05:48:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 6, 2022):

Welp, that's... not super helpful by itself. We've had another leak in recent memory, but also without a clear cause. I'm gonna leave this open for a week to see if you can find a repro. Of course, feel free to comment here if you find one even after that week.

@zadjii-msft commented on GitHub (Jun 6, 2022): Welp, that's... not super helpful by itself. We've had another leak in recent memory, but also without a clear cause. I'm gonna leave this open for a week to see if you can find a repro. Of course, feel free to comment here if you find one even after that week.
claunia commented 2026-01-31 05:48:50 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 6, 2022):

A fellow Process Hacker user! 😻

If you encounter such a bug again and would like to help us out, please consider using the "Create dump file..." option:
image

This process might take a few minutes and create a potentially very large .dmp file (up to ~9GB in your case), but it would help us a lot at finding the root cause. (Those .dmp files may contain private information and should only be shared privately / via mail however.)

@lhecker commented on GitHub (Jun 6, 2022): A fellow Process Hacker user! 😻 If you encounter such a bug again and would like to help us out, please consider using the "Create dump file..." option: ![image](https://user-images.githubusercontent.com/2256941/172193899-07af4cc2-abfc-431e-8e7d-57a7ccb983e1.png) This process might take a few minutes and create a potentially very large `.dmp` file (up to ~9GB in your case), but it would help us a lot at finding the root cause. (Those `.dmp` files may contain private information and should only be shared privately / via mail however.)
claunia commented 2026-01-31 05:48:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 10, 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 (Jun 10, 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**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#17646
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?