-
Notifications
You must be signed in to change notification settings - Fork 690
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
Sample-by-sample leak tests #10360
Labels
area/automation
Categorizes an issue or PR as relevant to project automation
area/performance 📈
Categorizes an issue or PR as relevant to performance
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
kind/enhancement
New feature or request
project/core-tools 🛠️
Categorizes an issue or PR as relevant to core and tools
Comments
MartinZikmund
added
kind/enhancement
New feature or request
triage/untriaged
Indicates an issue requires triaging or verification
difficulty/tbd
Categorizes an issue for which the difficulty level needs to be defined.
area/automation
Categorizes an issue or PR as relevant to project automation
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
and removed
triage/untriaged
Indicates an issue requires triaging or verification
difficulty/tbd
Categorizes an issue for which the difficulty level needs to be defined.
labels
Nov 7, 2022
jeromelaban
added
the
project/core-tools 🛠️
Categorizes an issue or PR as relevant to core and tools
label
Nov 8, 2022
Compiled a list of samples that currently either fail or leak. Very rudimentary test draft here - https://github.com/unoplatform/uno/tree/dev/mazi/extra-leak-tests
|
MartinZikmund
added
the
area/performance 📈
Categorizes an issue or PR as relevant to performance
label
Aug 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/automation
Categorizes an issue or PR as relevant to project automation
area/performance 📈
Categorizes an issue or PR as relevant to performance
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
kind/enhancement
New feature or request
project/core-tools 🛠️
Categorizes an issue or PR as relevant to core and tools
What would you like to be added:
Currently we have memory leak tests which verify very simple scenarios (e.g. default properties of each control). However, we already have samples app full of varied and extensive sample pages, each of them showcasing various controls and their features in detail. We could potentially run memory leak tests against each (or some - as some may be leaking intentionally), which would give us comprehensive account of whether controls/APIs leak memory in some real-world scenarios.
The test could just load and unload the sample page and verify whether anything remained in the memory after several GC collections.
Why is this needed:
Memory and perf.
For which Platform:
All
The text was updated successfully, but these errors were encountered: