xamarin/Xamarin.Forms

Android/UWP ListView Memory Leak

Open

#5,451 opened on Mar 5, 2019

View on GitHubContributor guide
 (5 comments) (2 reactions) (0 assignees)C# (1,926 forks)batch import
a/listviewa/performancee/7 :clock7:help wantedp/Androidp/UWPt/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

When updating ItemsSource for ListView cell views remains in memory both on Android(not so fast) and UWP(rapidly)

Steps to Reproduce

  1. Run sample app in Android/UWP
  2. Click a few times on any item
  3. Check debug output or diagnostic on UWM

Expected Behavior

Cell Views GC

Actual Behavior

Cells grow in memory

Sample Project: ListViewMemory.zip

Contributor guide

Research direction
Investigate the ListView cell recycling mechanism on Android and UWP; trace when cells are released from memory and identify why they remain after ItemsSource update.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Xamarin.FormsMemory Profiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40