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

Question: Has the OS bug fix for excessive TabViewItem memory usage shipped yet? #6979

Closed
lukeblevins opened this issue Apr 14, 2022 · 7 comments
Closed

Question: Has the OS bug fix for excessive TabViewItem memory usage shipped yet? #6979

lukeblevins opened this issue Apr 14, 2022 · 7 comments
Labels
no-issue-activity question

Comments

@lukeblevins
Copy link
Contributor

If not, is there a timeframe for when this will come to Windows or the decoupled UI stack?

Context: #3597 (comment)

FYI @StephenLPeters @RBrid
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Apr 14, 2022
@lukeblevins lukeblevins mentioned this issue Apr 15, 2022
Closed
@ojhad
Copy link
Contributor

ojhad commented Apr 25, 2022

@RBrid do you have any information on this?

@ojhad ojhad removed the needs-triage Issue needs to be triaged by the area owners label Apr 25, 2022
@RBrid
Copy link
Contributor

RBrid commented Apr 25, 2022

@lukeblevins , @ojhad , the last info I got was that an OS servicing release on May 17th would include this leak fix.

The fix has also been ported into WinUI3 / WinAppSDK on 4/18. So it looks like it will be part of WinAppSDK 1.1 Preview3.

@lukeblevins
Copy link
Contributor Author

@RBrid Was there an OS servicing release yesterday? Also did this fix ship in WinUI3 preview yet?

@lukeblevins lukeblevins mentioned this issue May 18, 2022
Closed
@lukeblevins
Copy link
Contributor Author

@ojhad @RBrid @StephenLPeters Any update?

@lukeblevins
Copy link
Contributor Author

@ojhad @RBrid @StephenLPeters Any update on this with v1.2 or v1.3?

@github-actions
Copy link

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@lukeblevins
Copy link
Contributor Author

Closing myself because this bug wasn't acknowledged by the WinUI team for over a year.

@lukeblevins lukeblevins closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
no-issue-activity question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ojhad @lukeblevins @RBrid