You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon installing Xamarin.AndroidX.ConstraintLayout in the application's source code, a memory leak related to ReportFragment from the androidx.lifecycle library is observed when navigating to a new activity and subsequently returning to the previous activity. This issue was replicated in a new .NET Android solution where only Xamarin.AndroidX.ConstraintLayout was installed. The memory leak was detected using the Android Studio profiler after navigating back to the previous activity. An attachment has been provided for reference.
Steps to Reproduce
Begin by creating a new .NET Android project.
Within the main activity page, add a button to facilitate the creation of a new activity.
Implement functionality to navigate to the new activity upon clicking the button.
Enable navigation back to the previous page by pressing the back button.
Repeat this process multiple times.
Capture a heap dump using the Android Studio profiler to identify any memory leaks.
After iterating the process x times, you should be able to identify x instances of memory leaks.
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Android application type
Android for .NET (net6.0-android, etc.)
Affected platform version
VS 17.11.2 dotnet 7.0 and dotnet 8.0
Description
Upon installing Xamarin.AndroidX.ConstraintLayout in the application's source code, a memory leak related to ReportFragment from the androidx.lifecycle library is observed when navigating to a new activity and subsequently returning to the previous activity. This issue was replicated in a new .NET Android solution where only Xamarin.AndroidX.ConstraintLayout was installed. The memory leak was detected using the Android Studio profiler after navigating back to the previous activity. An attachment has been provided for reference.
Steps to Reproduce
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: