{"action":"created","issue":{"url":"https://api.github.com/repos/PrismLibrary/Prism/issues/365","labels_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/365/labels{/name}","comments_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/365/comments","events_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/365/events","html_url":"https://github.com/PrismLibrary/Prism/issues/365","id":122824335,"number":365,"title":"Memory Leak with Navigation?","user":{"login":"billSpaulding","id":2274611,"avatar_url":"https://avatars.githubusercontent.com/u/2274611?v=3","gravatar_id":"","url":"https://api.github.com/users/billSpaulding","html_url":"https://github.com/billSpaulding","followers_url":"https://api.github.com/users/billSpaulding/followers","following_url":"https://api.github.com/users/billSpaulding/following{/other_user}","gists_url":"https://api.github.com/users/billSpaulding/gists{/gist_id}","starred_url":"https://api.github.com/users/billSpaulding/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/billSpaulding/subscriptions","organizations_url":"https://api.github.com/users/billSpaulding/orgs","repos_url":"https://api.github.com/users/billSpaulding/repos","events_url":"https://api.github.com/users/billSpaulding/events{/privacy}","received_events_url":"https://api.github.com/users/billSpaulding/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-17T21:14:07Z","updated_at":"2015-12-23T21:29:30Z","closed_at":"2015-12-17T21:29:50Z","body":"Hello,\r\n\r\n  There is what would appear to be a well known memory leak issue with Xamarin Forms (as well as Xamarin.IOS and Xamarin.Android)   especially during navigation. Some references below.\r\n\r\nAt least in my experiences (which seem to be similar to many others in the community) it is literally impossible to create a downward trend in memory consumption while navigating from page to page. Removing a page from the stack NEVER removes all the memory. The Heap is perpetually growing. This can be recreated with just about any view. Using a view that contains a list that implements a custom view cell will surface the problem immediately. \r\n\r\nQuestion I have is will migrating from the out-of-the-box navigation help with this or is  PRISM subject to the same issues ? (making the assumption you agree with the findings listed below in terms of there being an actual memory leak issue) \r\n\r\n\r\nhttp://stackoverflow.com/questions/25198762/is-this-a-memory-leak-in-xamarin-forms \r\nhttp://stackoverflow.com/questions/25532870/xamarin-ios-memory-leaks-everywhere \r\nhttps://bugzilla.xamarin.com/show_bug.cgi?id=21995 \r\nhttp://forums.xamarin.com/search?adv=&search=memory+leak+in+xamarin+forms&title=&author=&cat=all&tags=&discussion_d=1&discussion_question=1&comment_c=1&comment_answer=1&within=1+day&date=\r\n"},"comment":{"url":"https://api.github.com/repos/PrismLibrary/Prism/issues/comments/166992854","html_url":"https://github.com/PrismLibrary/Prism/issues/365#issuecomment-166992854","issue_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/365","id":166992854,"user":{"login":"JeffDalby","id":15741016,"avatar_url":"https://avatars.githubusercontent.com/u/15741016?v=3","gravatar_id":"","url":"https://api.github.com/users/JeffDalby","html_url":"https://github.com/JeffDalby","followers_url":"https://api.github.com/users/JeffDalby/followers","following_url":"https://api.github.com/users/JeffDalby/following{/other_user}","gists_url":"https://api.github.com/users/JeffDalby/gists{/gist_id}","starred_url":"https://api.github.com/users/JeffDalby/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeffDalby/subscriptions","organizations_url":"https://api.github.com/users/JeffDalby/orgs","repos_url":"https://api.github.com/users/JeffDalby/repos","events_url":"https://api.github.com/users/JeffDalby/events{/privacy}","received_events_url":"https://api.github.com/users/JeffDalby/received_events","type":"User","site_admin":false},"created_at":"2015-12-23T21:29:30Z","updated_at":"2015-12-23T21:29:30Z","body":"Just to add I created a test project using the latest Prism XF with two pages, each having a binding for a label, and single button calling a delegate command to navigate to the other page and a small image.  Just clicking the buttons to navigate back and forth between the two pages will crash the app in about two minutes as memory climbs with each click.\r\n\r\nI've sent a copy of the solution to Xamarin Support and will update this with what they find."}}