Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I have found that a unbound memory growth while using Navigation page in Xamarin.Forms
Create a Master-Details sample, In master page a simple button to child page.
In child page, create a list view containing label (followed this tutorial- https://developer.xamarin.com/api/property/Xamarin.Forms.ListView.GroupDisplayBinding/ )
Just run the app,It is captured in Instruments for memory issues.
'It release memory for the listview but not for the labels rendered inside the listview'
Could you please tell me how to fix this issue?
Note: This isue also exist in custom controls too. I have tried for Dispose and Disappearing methods too but no use.
@Gobi, As per your bug description, I have checked this issue with Forms Sample https://github.com/xamarin/xamarin-forms-samples/tree/master/Navigation/MasterDetailPage and at my end its working fine. I am not getting an unbound memory growth while using this sample.
Screencast : http://www.screencast.com/t/iyAGBkr7gM
App Output : https://gist.github.com/Arpit360/1ce9af2d17b22c697bdcd7f90439c239
Could you please provide me the project & logs details, & steps to reproduce this issue.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!