Bug 34756 - Diabolical WinPhone ListView Memory Leak
Summary: Diabolical WinPhone ListView Memory Leak
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-10-11 22:41 UTC by Adam
Modified: 2017-03-11 03:44 UTC (History)
7 users (show)

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

Reproduction (168.68 KB, application/x-zip-compressed)
2015-10-11 22:42 UTC, Adam

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 Adam 2015-10-11 22:41:28 UTC
This is another memory leak on Windows Phone different from the other one I submitted.

As you will see in the Repro attached, if you have a ListView with 21 items or less (it may be a memory related not sure) you can scroll up and down the listview with a small increase in memory then it goes back down as the cells go out of view.

If you have 22 items or more in the listview the memory continues to go up as you scroll up and down, never releasing any memory.
Comment 1 Adam 2015-10-11 22:42:06 UTC
Created attachment 13280 [details]
Comment 2 Adam 2015-10-13 20:38:57 UTC
And I would appreciate if this one could be marked critical. Our Windows Phone app is critical to a few clients, they have many Nokia Lumia's for their staff to use and they can't use it for more than 5-10 minutes without it crashing. Or if you can let me know of a workaround, either way.
Comment 4 Adam 2017-03-11 03:44:02 UTC
Considering WinPhone is sunsetting and this report is about 1.5yrs old, I don't expect this to ever be resolved. I also no longer use WinPhone.

Marking as Resolved and Not On Roadmap