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.
Created attachment 17352 [details]
Shows glitches in the colors of ListView cells
We have created a reduced test case project that shows incorrect rendering (and possible leaks) using ListViews with an ItemsSourceProperty binding on Win8.1.
Please see our public repository with the test case : https://bitbucket.org/luminixinc/xamarintest (ListViewsPerfTest branch using the ListViewsPerfTest/ListViewsPerfTest.sln project).
Both tests should be done with Windows 8.1 target (Note that UWP also appears to show the same/similar problems).
Test #1 : Enter the ListView test page and witness that some cells do not correctly draw subsequent colors (R,G,B in that order repeating). Sometimes a color is repeated or skipped.
- You may need to return to home page and then re-enter the ListView test page to trigger the behavior
- Scrolling rapidly top-to-bottom appears to be more likely to trigger the erroneous rendering
Test #2 : Build in release mode and start Debug > Performance Profiler... Choose 'Memory Usage' and start the diagnostics session. On the ListView page, aggressively scroll the view top-to-bottom and watch the memory grow (despite bounded number of cells). Witness what appears to be unbounded memory growth despite GC events during scrolling.
- Returning to the home page and re-entering ListView test page once does not appear to clear the allocated memory
- However returning to the home page and re-entering the ListView test page 'a few more times' does appear to clear a significant portion of the allocated memory, but does not appear to clear *all* of it
PullReq improvements/fixes to this test case are most welcome, thanks!
WP8 and 8.1 have been deprecated and as such this work is no longer on our roadmap.