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

Severe memory leak with Desktop Window Manager #2468

Closed
radu-matei opened this issue Aug 18, 2019 · 3 comments
Closed

Severe memory leak with Desktop Window Manager #2468

radu-matei opened this issue Aug 18, 2019 · 3 comments
Labels
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

@radu-matei
Copy link

radu-matei commented Aug 18, 2019 •
edited

Environment

Windows build number: Windows [Version 10.0.18963.1000]
Windows Terminal version (if applicable): installed from Store

Any other software?
Ubuntu on WSL2

Steps to reproduce

  • open an Ubuntu tab in the Terminal

  • the memory allocated to the Desktop Window Manager starts growing

  • it grows at a rate of around 1 GB / 10 seconds without stopping

image

  • closing the WSL2 tab and opening another one (PowerShell for example), the issue goes away.
  • using the same WSL2 distro and shell from another terminal app (VS Code, for example), issue is not present.

Just upgraded to 18963, mostly similar setup worked fine for 18950.

EDIT: The issue goes away after turning useAcrylic off.
@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 Aug 18, 2019
@DHowett-MSFT
Copy link
Contributor

Actually, we’ve been seeing reports of this on newer insider builds of windows regardless of WT being used 😄 thanks!

@radu-matei
Copy link
Author

radu-matei commented Aug 18, 2019 •
edited

I can confirm this is not a terminal issue, but a Windows one, related to transparency settings.

Closing - thanks a lot for the hint!

@radu-matei
Copy link
Author

FWIW, I created an issue in the Feedback Hub - if anyone else experiences this, disabling all transparency settings is a known workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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
2 participants
@radu-matei @DHowett-MSFT