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

WSA may have memory leakage and WSA occupies double the RAM #549

Open
Vector2053 opened this issue Mar 26, 2024 · 0 comments
Open

WSA may have memory leakage and WSA occupies double the RAM #549

Vector2053 opened this issue Mar 26, 2024 · 0 comments
Labels
bug Default bug tag for tracking triage-needed For issues raised to be triaged and prioritized by internal Microsoft teams

Comments

@Vector2053
Copy link

Steps to reproduce

I have set a maximum of 2GB of RAM for wsa.When wsa is running, vmmem occupies 2GB of RAM, but wsaClient still occupies a considerable amount of RAM。The RAM,which is occupied by wsaClient, is directly allocated by Windows, not used in vmmem.Ｏver time, it will occupy more and more RAM. Unless WSA is closed, it will not recycle RAM.

✔️ Expected Behavior

WsaClient should not occupy extra RAM

❌ Actual Behavior

WsaClient occupies extra RAM,and it will not recycle RAM.
Snipaste_2024-03-26_22-25-14
Snipaste_2024-03-26_22-25-57

Other Software

No response

Please specify the version of Windows Subsystem for Android

2311.40000.5
@Vector2053 Vector2053 added bug Default bug tag for tracking triage-needed For issues raised to be triaged and prioritized by internal Microsoft teams labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Default bug tag for tracking triage-needed For issues raised to be triaged and prioritized by internal Microsoft teams
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Vector2053