Bug 27444 - The SurfaceDestroyed method does not get called as soon as another page is placed on top of it
Summary: The SurfaceDestroyed method does not get called as soon as another page is pl...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.4
Hardware: PC Mac OS
: Normal major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-02-25 19:48 UTC by Ian Leatherbury
Modified: 2015-02-27 05:38 UTC (History)
5 users (show)

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:

Description Ian Leatherbury 2015-02-25 19:48:48 UTC
Found in this forum post: https://forums.xamarin.com/discussion/33708/custom-renderer-surface-not-destructed-nor-disposed

Repro case here: https://github.com/rebuy-de/xamarin-custom-view-renderer

Current workaround involves using OnVisibilityChanged():

protected override void OnVisibilityChanged(global::Android.Views.View view, ViewStates visibility)
    base.OnVisibilityChanged(view, visibility);

    if (visibility == ViewStates.Visible) {
        // just in case do visible stuff here

    if (visibility == ViewStates.Gone) {
        // run surfaceDestroy logic here also!
Comment 1 Parmendra Kumar 2015-02-26 06:10:11 UTC
I have checked this issue and observed that SurfaceDestroyed method does not get called. To reproduce this issue I have followed the attached sample project.

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

AppOutput Log: https://gist.github.com/Parmendrak/c417dae950216fe148b8
IDE Log: https://gist.github.com/Parmendrak/e9392696af3c5984fded

Please let me know if I can give more information regarding same.

Environment info:


=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 1a096c6f-0678-402e-89b2-a2c10f7e80e4
	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: (Business Edition)
Hash: 98ee412
Build date: 2015-02-11 04:37:05-0500

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin.Android ===

Version: (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 Jason Smith [MSFT] 2015-02-27 05:38:51 UTC
The backstack is not destroyed when you navigate away from it, only items popped from the stack. We may choose to modify this in the future but this is currently the case.