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.

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

Memory leak on window resize #5016

Closed
seanhelling opened this issue Mar 19, 2020 · 2 comments
Closed

Memory leak on window resize #5016

seanhelling opened this issue Mar 19, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@seanhelling
Copy link

Environment

Windows build number: 10.0.19555.0
Windows Terminal version (if applicable): 0.10.761.0

Any other software?
zsh on WSL, oh-my-zsh

Steps to reproduce

  1. Open Terminal
  2. Resize window

Expected behavior

A resized window that continues to function properly

Actual behavior

Window is resized, Terminal consumes entirety of system memory and stops responding
terminal-leak

This issue is novel to the Windows Store update that was pushed to me this morning.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 19, 2020
@zadjii-msft
Copy link
Member

Thanks for the report! This is actually tracked buy a bunch of other issues on this repo already: #4972, #4978, and the root cause #2815. In fact, this one's already fixed too, see PR #4964, which should be getting pushed out later today.

/dupe #4972 #4978 #2815

@ghost
Copy link

ghost commented Mar 19, 2020

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 ghost closed this as completed Mar 19, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 19, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants