Bug 8546 - Memory profiling to track and unload unused views during memory snapshot.
Summary: Memory profiling to track and unload unused views during memory snapshot.
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 6.1.x
Hardware: Macintosh Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Reported: 2012-11-21 12:50 UTC by Andrew Way
Modified: 2015-04-16 10:36 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Andrew Way 2012-11-21 12:50:10 UTC
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.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2015-04-16 10:36:24 UTC
This should be fairly easy to track down already with the new profiler.