Memory Leak on back and Fro navigation on page where Custom control and complex View Page

[thanigaiharan]

Description

We have a Vehicle Summary page with Below details as shown in Gif.

 Custom Control (Vehicle Layout where we show Vehicle structure with Tires in colors)
 Dynamically Created Template to show each Tire Details (1-1, 1-2 … ), we used bindableLayout with Vertical StackLayout to dynamically generate the template.
 Odometer details Section
 Vehicle Info Section.

Navigation works as shown below. Here when we Navigate from Vehicle List Page -> Vehicle Summary page -> On Back Click -> Vehicle list Page

Issue:

1. If we navigate between these two pages (Back and Fro Navigation ) , we are seeing the application memory is keep on increasing.
2. VehicleLayout Custom control is using event handlers to create Controls dynamically based on the Property from Viewmodel, we identified one of the event is not unsubscribed properly so we tried with replacing events with weakreference, but still the memory is increasing.
3. Bindable Layout is also taking lot of time to load and display in Page.

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

8.0.10 SR3

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

[dotnet-policy-service]

Hi @thanigaiharan. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback to reproduce the issue but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.