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.
With ViewDidUnload() obsolete(and no longer being called by iOS) views are now programmed not to release data object until DidReceiveMemoryWarning() is called. Testing for memory leaks is made more difficult when unused views are not releasing data objects. It would probably be a good feature to track unused views during memory profiling and tell them to unload during a memory snapshot.
This should be fairly easy to track down already with the new profiler.