Bug 56562 - Listview scrolling getting stuck while I am using relative layout in viewcell (In Android)
Summary: Listview scrolling getting stuck while I am using relative layout in viewcell...
Status: RESOLVED DUPLICATE of bug 56240
Alias: None
Product: Android
Classification: Xamarin
Component: General (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on: 56240
  Show dependency tree
Reported: 2017-05-17 12:43 UTC by Abdul Mujeeb Khan
Modified: 2017-06-23 19:20 UTC (History)
5 users (show)

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

Project (1.29 KB, application/zip)
2017-05-17 12:47 UTC, Abdul Mujeeb Khan
RelativeLayout Perf Issue Sample Project (111.75 KB, application/x-zip-compressed)
2017-05-25 02:18 UTC, Lee Richardson

Description Abdul Mujeeb Khan 2017-05-17 12:43:00 UTC
Listview scrolling getting stuck while I am using relative layout in viewcell. Earlier it was working fine, but I think because of updating nuget packages or Xamarin studio, this issue arised. (In Android)

Now while scrolling very first time in this case, Scrolling get stuck after some time it scrolls smooth.

Alternatively If i use Stack layout instead of relative layout, listview scrolls smooth, But i need relative layout.

    Xamarin.forms :

    Xamarin Studio Community
    Version 6.3 (build 864)
    Installation UUID: f9acdb29-2b13-4556-9887-824b8e4e0693
    Mono (2017-02/9667aa6) (64-bit)
    GTK+ 2.24.23 (Raleigh theme)

    Package version: 500000100

    Version: (Xamarin Studio Community)
    Hash: 3e5ac5ff
    Branch: d15-2
    Build date: 2017-05-05 18:11:38-0400

    Version: (Xamarin Studio Community)
    Android SDK: /Users/abdul/Andoid-SDK-s/android-sdk-macosx
    Supported Android versions:
    4.4 (API level 19)
    5.0 (API level 21)
    6.0 (API level 23)
    7.0 (API level 24)
    7.1 (API level 25)

SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.4
SDK Build Tools Version: 24.0.3

    Java SDK: /usr
    java version "1.8.0_111"
    Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
    Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
Comment 1 Abdul Mujeeb Khan 2017-05-17 12:47:34 UTC
Created attachment 22229 [details]
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2017-05-17 18:48:01 UTC
## Note to the Xamarin team

This sounds potentially related to Bug 56240?  Perhaps once candidate builds are available that resolve Bug 56240, it would be good to have the reporter of this Bug 56562 check if those builds resolve this issue as well.
Comment 3 Lee Richardson 2017-05-25 02:13:50 UTC
I've noticed the same issue.  The RelativeLayout performance in a custom ViewCell of a ListView is virtually unusable on Android, but fine in iOS.

I already started writing up a ticket before I found this one, so I'm including my sample project as a 2nd data point.
Comment 4 Lee Richardson 2017-05-25 02:18:21 UTC
Created attachment 22439 [details]
RelativeLayout Perf Issue Sample Project

In XfRelativeLayoutIssue\MainPage.cs it uses a RelativeLayout in a custom ViewCell of a ListView.  When you run this on Android (API 22 anyway) the performance is virtually unusable.
Comment 5 Jon Douglas [MSFT] 2017-06-23 19:20:39 UTC
I've tested both 




And it seems the performance is fine. I believe based on the fix in https://bugzilla.xamarin.com/show_bug.cgi?id=56562#c2 that has resolved this issue. Thus I am marking this bug as a DUPLICATE of https://bugzilla.xamarin.com/show_bug.cgi?id=56240

Version Information:

Microsoft Visual Studio Enterprise 2017 
Version 15.2 (26430.13) Release
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Enterprise

Xamarin (fec6f88)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK (ad35de4)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

*** This bug has been marked as a duplicate of bug 56240 ***

Note You need to log in before you can comment on or make changes to this bug.