You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The RippleHost Eventhandlers do not get properly removed, causing references to already deleted objects to persist forever, and not being garbage collected.
To Reproduce
Steps to reproduce the behavior:
Create a new Adonis Window
Add a ListView, add a Button as ListView.ItemTemplate (to have the ripple effect)
Bind the List to an ObservableCollection with any Object
Add a new Item to the List, and then remove it => Item stays in memory forever and is never garbage collected
Expected behavior
Proper removal of all eventhandlers to allowed already removed objects to be garbage collected
*Additional Info
Inspected using .net Memory Profiler
The text was updated successfully, but these errors were encountered:
I created a sample app that reproduces that issue, just start it and wait, the memory will get more and more every second, even though the number of items displayed stays the same
Just stumbled upon the same issue.
I have a list which I switch out at runtime that can have a lot of UserControls that I use a button on for the Spotlight effect.
I noticed that the memory went up if I switched the lists. Would be nice to get a fix for that.
For anyone looking for a "fix". This is my App.xaml which includes all default Ressources, but the Button.xaml explicitly without the ripple effect, so no more memory leaks:
Describe the bug
The RippleHost Eventhandlers do not get properly removed, causing references to already deleted objects to persist forever, and not being garbage collected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Proper removal of all eventhandlers to allowed already removed objects to be garbage collected
*Additional Info
Inspected using .net Memory Profiler
The text was updated successfully, but these errors were encountered: