-
Notifications
You must be signed in to change notification settings - Fork 561
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
[UWP][Memory] [Rendered Cards Leaking Memory] #3425
Comments
@RebeccaAnne, could you take a stab at this see if this is something that @paulcam206 has already addressed or a different one at this point (see offline email thread on this as well) ? Thanks ! |
Started investigation, found a few things.
|
I am able to repro a leak with the above card against the 1.0.0 nuget package. |
Thanks @RebeccaAnne. @andycb it appears that the leak is something that has existed since at least 2017 if not longer. We'll be looking into investigating the cause and mitigating in a subsequent patch (likely early next month if not sooner) though it likely will not make the Sept patch which is supposed to be code complete in the next couple of days. We'll keep you posted. Thanks |
Not sure if it's the leak, but I'm addressing a couple leaks
in #3457 |
and quite a few more |
This issue has been automatically marked as stale because it has not had any activity for 5 days. |
Hi. Is there any planned work to look further in to the remaining leaks? |
@barryptak Maybe @shalinijoshi19 have an update on this one... |
@paulcam206 could you double check here see if you can still repro it release/1.2 bits (or the latest released).Thanks |
Addressing this issue is not currently on our roadmap, so closing. Please feel free to continue the conversation in this issue for future consideration. |
Hey, @paulcam206. Thanks! |
Platform
Version of SDK
AdaptiveCards.Redering.Uwp V1.2.2
Details
When redering an adaptive card, it appears that its memory is not released. The bellow code sample loads an adaptive card, displays it on the UI before removing it and forcing a garbage collection. After 50 itteraltions, an additional 90MB of memory is being used by the test app.
The text was updated successfully, but these errors were encountered: