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

net8 sr9 Win Platform Release Mode Memory leak when multiple windows get closed #24803

Open
jingliancui opened this issue Sep 17, 2024 · 5 comments
Labels
memory-leak 💦 Memory usage grows / objects live forever p/2 Work that is important, but is currently not scheduled for release platform/windows 🪟 t/bug Something isn't working

Comments

@jingliancui
Copy link
Contributor

jingliancui commented Sep 17, 2024

Description

1.App will crash in release mode when the memory increase more than 300M which is shown in task manager.

2.1Additional info for publish debug app:
App will crash after 3 time to do : new 100 windows, then close all.
Situation better then Release mode, but not better, due to my laptop has 50G Ram, but debug app will crash in about 400M

2.2Additional info for debug using VS:
In the 3rd time to do : new 100 windows, then close all, VS show this
image

Steps to Reproduce

1.Publish the release app:
dotnet publish -f net8.0-windows10.0.19041.0 -p:RuntimeIdentifierOverride=win10-x64 -p:WindowsPackageType=None -p:WindowsAppSDKSelfContained=true

2.Open the APP

3.Input a number 50 to the Entry Control

4.Click the button "new windows"

5.Click the button "Close all windows"

Repeat step3 to step5 about 3 time, the app will crash

Link to public reproduction project repository

https://github.com/jingliancui/MAUIWinUIWinMemoryLeakIssue

Version with bug

8.0.90 SR9

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

No response

Did you find any workaround?

No

Relevant log output

No response

@jingliancui jingliancui added the t/bug Something isn't working label Sep 17, 2024
Copy link
Contributor

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@MartyIX MartyIX added platform/windows 🪟 memory-leak 💦 Memory usage grows / objects live forever labels Sep 17, 2024
@tj-devel709 tj-devel709 added the p/2 Work that is important, but is currently not scheduled for release label Sep 17, 2024
@tj-devel709 tj-devel709 added this to the .NET 9 Planning milestone Sep 17, 2024
@tj-devel709
Copy link
Contributor

Hi @jonathanpeppers, do you have thoughts on this one?

@jingliancui
Copy link
Contributor Author

I'm curious about in debug within vs #24802, it doesn't crash.
Let me try if it will crash if publish using debug mode.

@jingliancui
Copy link
Contributor Author

Additional info for publish debug app:
App will crash after 3 time to do : new 100 windows, then close all.
Situation better then Release mode, but not better, due to my laptop has 50G Ram, but debug app will crash in about 400M .
Also updated this info to the first description.

@jingliancui
Copy link
Contributor Author

Additional info for debug using VS:
In the 3rd time to do : new 100 windows, then close all, VS show this
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
memory-leak 💦 Memory usage grows / objects live forever p/2 Work that is important, but is currently not scheduled for release platform/windows 🪟 t/bug Something isn't working
3 participants