-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
BindableObjects not getting collected causing memory leak, android #24478
Comments
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! Open similar issues:
Closed similar issues:
|
I had problems with SetterSpecificiityList when used BindableLayout and loaded itemtemplate in non ui thread. |
@Toomas75 Were you seeing similar issues as to what I mentioned? If so how did you get around it? Thanks :) |
Just checked my history. It wasn't views leaking problem as you experience. |
Description
I have a pretty large application that we migrated over from xamarin to MAUI. Seems that after navigating through our app x~40 times we end up with a memory leak causing the application to hang. I've collected memory dumps at the time of the crash which I'll post here.
I can see that MIcrosoft.Maui.Controls.SetterSpecificiityList and BindablePropertyContext seem to be eating up a bunch of our resources as dead objects. I was wondering if there was a way to get these bindings to be cleaned up by the GC as I believe these seem to be the cause of our memory leak? I've tried traversing through the visual tree, removing handlers, setting binding context to null, setting the styles to null, unapplying bindings upon disposal. Can't see to get any progress on resolving this issue.
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
8.0.21 SR4.1
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No workaround yet.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: