Bug 27121 - [Android] Custom Cell in ListView Choppy/Performance Issue
Summary: [Android] Custom Cell in ListView Choppy/Performance Issue
Status: RESOLVED NORESPONSE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.4
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-02-17 00:26 UTC by Cody Beyer (MSFT)
Modified: 2017-06-17 00:43 UTC (History)
10 users (show)

Tags: android, listview, memory, performance, viewcell
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:
Status:
RESOLVED NORESPONSE

Description Cody Beyer (MSFT) 2015-02-17 00:26:56 UTC
### Description

The following app modifies the sample to use a custom cell in a list view. There appears to be a memory leak in doing so

### Test Case

https://www.dropbox.com/s/ez18sbnqtg8akqg/ExtendedCells.zip?dl=0

### Steps to Reproduce

1. Download test case
2. Deploy to Android Emulator
3. Interact with list view

### Expected Results

The list view "keeps up" with your interaction, and navigates smoothly. 

### Actual Results

The ListView gets choppy

### Version

=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 33d88ac5-6a46-48da-ae18-b355ffac4d9e
Runtime:
	Mono 3.12.0 ((detached/de2f33f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000076

=== Apple Developer Tools ===

Xcode 6.1.1 (6611)
Build 6A2008a

=== Xamarin.iOS ===

Version: 8.6.2.15 (Business Edition)
Hash: 446339d
Branch: 
Build date: 2015-02-13 00:33:07-0500

=== Xamarin.Mac ===

Not Installed

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.10.2
Darwin Codys-MacBook-Pro.local 14.1.0 Darwin Kernel Version 14.1.0
    Mon Dec 22 23:10:38 PST 2014
    root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64
Comment 1 Parmendra Kumar 2015-02-17 06:28:58 UTC
I have checked this issue and I am getting same behavior mentioned in the bug description.

Screencast for the same:http://www.screencast.com/t/RsEESFjjKLsl

Please let we know if I can give more information regarding this.

XampLog: https://gist.github.com/Parmendrak/d6e028f03ec994925009
ApplicationOutput Log:https://gist.github.com/Parmendrak/595d402826c8ecc9c97b
IdeLog:https://gist.github.com/Parmendrak/ba2fafe18d6d76cfffd4

Environment info:

Xamarin.Forms version: 1.3.4.6331-pre4
=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 1a096c6f-0678-402e-89b2-a2c10f7e80e4
Runtime:
	Mono 3.12.0 ((detached/de2f33f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000076

=== Apple Developer Tools ===

Xcode 6.1.1 (6611)
Build 6A2008a

=== Xamarin.iOS ===

Version: 8.6.1.20 (Business Edition)
Hash: 3b3ef43
Branch: 
Build date: 2015-01-24 09:42:21-0500

=== Xamarin.Mac ===

Version: 1.10.0.18 (Business Edition)

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/360_macmini/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.9.4
Darwin ShrutiMac.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 2 ppatarinski@paylocity.com 2015-02-17 10:14:02 UTC
One more thing I would like to add is that the choppiness is present not only with the Native Custom Cell, but also with the Xamarin Forms ViewCell using a StackLayout. Also there is strange behavior present on Win Phone as well.
Comment 3 ppatarinski@paylocity.com 2015-04-30 11:32:02 UTC
Any update on this?
Comment 4 Seth Rosetter 2015-05-28 15:00:17 UTC
Cody,

The sample is missing. Can you attach it again?
Comment 5 E.Z. Hart [MSFT] 2016-04-08 18:45:33 UTC
Code,

Can you post the sample again? The link is a 404.
Comment 6 Emanuele Sabetta 2016-11-12 10:51:48 UTC
I can confirm this. If I use a custom cell (or even a complex ViewCell) after a while the listview becomes unusable.
Comment 7 David Ortinau [MSFT] 2017-06-17 00:42:03 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information and a reproduction project. Thanks!