Severe memory leak with Desktop Window Manager #3471

Closed
opened 2026-01-30 23:22:08 +00:00 by claunia · 3 comments
Owner

Originally created by @radu-matei on GitHub (Aug 18, 2019).

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.

Originally created by @radu-matei on GitHub (Aug 18, 2019). # Environment ```none 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](https://user-images.githubusercontent.com/13103165/63218560-3fa34380-c166-11e9-8836-efb1f8d7b459.png) - 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.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:22:08 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Aug 18, 2019):

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

@DHowett-MSFT commented on GitHub (Aug 18, 2019): Actually, we’ve been seeing reports of this on newer insider builds of windows regardless of WT being used :smile: thanks!
Author
Owner

@radu-matei commented on GitHub (Aug 18, 2019):

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 commented on GitHub (Aug 18, 2019): I can confirm this is not a terminal issue, but a Windows one, related to transparency settings. Closing - thanks a lot for the hint!
Author
Owner

@radu-matei commented on GitHub (Aug 18, 2019):

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

@radu-matei commented on GitHub (Aug 18, 2019): FWIW, I created an [issue in the Feedback Hub](https://aka.ms/AA5vuqw) - if anyone else experiences this, disabling all transparency settings is a known workaround.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3471