xamarin/Xamarin.Forms

Webviews aren't being garbage collected when the containing page is popped

Open

#1,430 opened on Dec 20, 2017

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
a/webviewe/2 :clock2:good first issuehacktoberfest 🍻help wantedp/Androidt/bug :bug:up-for-grabs

Repository metrics

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

Description

Migrated from https://bugzilla.xamarin.com/show_bug.cgi?id=55749

Description

In the sample program, ThirdPage contains a webview defined in the xaml. Nothing is done to the webview in the code. Run the program and press the ThirdPage button, then the back arrow, 5 times and look at the memory allocations - there are 5 instances of the ThirdPage, WebView, WebViewRenderer, and WebClient (snapshot1 in the attached file). Not tap the button to garbage collect. The instances of ThirdPage and WebView drops to one, but WebViewRenderer and WebViewClient are still 5 (snapshot2). Why aren't these garbage collected?

Basic Information

  • Version with issue: 2.3.4

Reproduction Link

MemoryTest0.zip

Contributor guide

Research direction
Investigate why WebViewRenderer and WebViewClient instances are not garbage collected when the page is popped, focusing on the native renderer lifecycle and event handlers that may prevent collection.
Tech stack
csharpandroidios
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70