flayout navigation - how to deal with rasing memory?

Dani_S 3,316

Hi,

I used flayout navigation. when navigate beween pages it consume alot of memory.

In net 8. Not relase the previous page.

Does to use GC.Collect()?

Is allowed ?

Thanks,

  public void Navigate(string navigateTo)

  {


  if (navigateTo == "InProcessPage")

  {

      var page = (Page)Activator.CreateInstance(typeof(InProcessPage));

      if (page != null)

      {

          this.Detail = new NavigationPage(page);

          NavigationPage.SetHasBackButton(Detail, false);

          inProcessButton.HasSelect = true;

          uploadButton.HasSelect = false;

          downloadButton.HasSelect = false;

          copyButton.HasSelect = false;

          scanHistoryButton.HasSelect = false;

          rulesButton.HasSelect = false;

          logsButton.HasSelect = false;

      }

  }

  else if (navigateTo == "DownloadPage")

  {

      var page = (Page)Activator.CreateInstance(typeof(DownloadPage));

      if (page != null)

      {

          this.Detail = new NavigationPage(page);

          NavigationPage.SetHasBackButton(Detail, false);

          downloadButton.HasSelect = true;

          uploadButton.HasSelect = false;

          inProcessButton.HasSelect = false;

          copyButton.HasSelect = false;

          scanHistoryButton.HasSelect = false;

          rulesButton.HasSelect = false;

          logsButton.HasSelect = false;

      }

  }

  else if (navigateTo == "CopyPage")

  {

      var page = (Page)Activator.CreateInstance(typeof(CopyPage));

      if (page != null)

      {

          this.Detail = new NavigationPage(page);

          NavigationPage.SetHasBackButton(Detail, false);

          copyButton.HasSelect = true;

          uploadButton.HasSelect = false;

          downloadButton.HasSelect = false;

          inProcessButton.HasSelect = false;

          scanHistoryButton.HasSelect = false;

          rulesButton.HasSelect = false;

          logsButton.HasSelect = false;

      }

  }

  **GC.Collect();**
```  }

Dani_S 3,316 Reputation points

2024-07-15T06:36:34.6433333+00:00

Does to use:

Try call System.GC.Collect(GC.MaxGeneration, GCCollectionMode.Forced, true, true) after navigating to page if the memory increase still happens like that you got memory leaks

from link:https://github.com/dotnet/maui/issues/15257
Dani_S 3,316 Reputation points

2024-07-15T06:36:46.1533333+00:00

....,
Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-15T06:56:15.39+00:00

Please use new InProcessPage() way to create a page, then navigate it.

Which method that you use to navigated to new page? Navigation.PushAsync(new Page()); or .NET MAUI Shell navigation
Dani_S 3,316 Reputation points

2024-07-15T07:16:12.9533333+00:00
I used new InProcessPage() way to create a page, why to create throguh activator class?

I'm using flayout navigation i can't use: Navigation.PushAsync(new Page()); or .NET MAUI Shell navigation

Does to use:

Try call System.GC.Collect(GC.MaxGeneration, GCCollectionMode.Forced, true, true) after navigating to page if the memory increase still happens like that you got memory leaks from link:https://github.com/dotnet/maui/issues/15257
Dani_S 3,316 Reputation points

2024-07-15T07:16:36.5233333+00:00

Your quick answer will be apreciated.
Dani_S 3,316 Reputation points

2024-07-15T07:36:11.4133333+00:00

This is my navigation:

if (page != null) { this.Detail = new NavigationPage(page); NavigationPage.SetHasBackButton(Detail, false);
Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-15T08:51:38.99+00:00

Which platform do you have this issue? https://github.com/dotnet/maui/issues/15257 this issue happened in the android platform.
Dani_S 3,316 Reputation points

2024-07-15T09:03:42.69+00:00

windows. waiting to your answer.
Dani_S 3,316 Reputation points

2024-07-15T09:28:26.8733333+00:00
I used new InProcessPage() way to create a page, why to create throguh activator class?

I'm using flayout navigation i can't use: Navigation.PushAsync(new Page()); or .NET MAUI Shell navigation

Does to use:

Try call System.GC.Collect(GC.MaxGeneration, GCCollectionMode.Forced, true, true) after navigating to page if the memory increase still happens like that you got memory leaks from link:https://github.com/dotnet/maui/issues/15257
Dani_S 3,316 Reputation points

2024-07-15T09:34:30.6433333+00:00

waiting to your answer.
Dani_S 3,316 Reputation points

2024-07-15T09:48:25.54+00:00
maybe using WeakReference pageReference = new WeakReference(page);
Dani_S 3,316 Reputation points

2024-07-15T10:09:53.8166667+00:00
maybe using

GC.Collect();
Dani_S 3,316 Reputation points

2024-07-15T10:22:44.16+00:00

waiting to your answer please.
Dani_S 3,316 Reputation points

2024-07-15T12:19:06.4266667+00:00

The memory increase all times!! when navigating beween pages.
Dani_S 3,316 Reputation points

2024-07-15T12:21:24.81+00:00

What is the solution ?
Dani_S 3,316 Reputation points

2024-07-15T20:35:10.6733333+00:00

Your quick answer will be appreciated.
Dani_S 3,316 Reputation points

2024-07-16T03:08:10.8366667+00:00

Waiting to your answer please.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dani_S 3,316 Reputation points

2024-07-16T07:17:25.92+00:00

Hi,

I took snapshots after navigating to page 1.

I took snapshots after navigating to page 2.

page 2 not relased.

How can i fixed it?
Dani_S 3,316 Reputation points

2024-07-16T07:21:44.8333333+00:00

Please look https://stackoverflow.com/questions/76739030/prior-pages-are-still-active-and-never-disposed

Does using serviice locator pattern and set the all pages as singelton will solved me the problem?
Dani_S 3,316 Reputation points

2024-07-16T07:22:07.5233333+00:00

YOur quick answer will be appreciated

Dani_S 3,316

Does this lines mean that 4 pages are cached in memory all times?

// Cache Pages
        builder.Services.AddSingleton<InitialPage>();
        builder.Services.AddSingleton<Page1>();        
        builder.Services.AddSingleton<Page2>();
        builder.Services.AddSingleton<Page3>();

Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-16T07:40:13.26+00:00

I took snapshots after navigating to page 1.I took snapshots after navigating to page page 2 not relased.

Do you mean that memory not rising in the page2? If so, the memory is reclaimed. rasing memory issue is solved, why you need to fix it?

Does this lines mean that 4 pages are cached in memory all times?

Yes, but I do not recommend you set all pages to singleton, if you set it, it will creates a single instance of the object which will remain for the lifetime of the app. If some objects(such as System.IO.File) in these pages are not destroyed explicitly, memory leaks will occur.
Dani_S 3,316 Reputation points

2024-07-16T07:55:13.37+00:00

Sorry:

I took snapshots after navigating to page 1.

I took snapshots after navigating to page 2=> page 1 not relased + page2.

es, but I do not recommend you set all pages to singleton, if you set it, it will creates a single instance of the object which will remain for the lifetime of the app. If some objects(such as System.IO.File) in these pages are not destroyed explicitly, memory leaks will occur.

So what to do ?

To do:

Cache Pages

builder.Services.AddTransient<InitialPage>();

builder.Services.AddSingleton<Page1>();

builder.Services.AddSingleton<Page2>();

builder.Services.AddTransient<ViewModelInitialPage>()

builder.Services.AddTransient<ViewModelPage1>()

builder.Services.AddTransient<ViewModelPage2>()

Your quick answer will be appreciated.
Dani_S 3,316 Reputation points

2024-07-16T07:57:08.4633333+00:00

See i navigate beween some pages and upload was first page and still in memory.
Dani_S 3,316 Reputation points

2024-07-16T08:28:30.9966667+00:00

Pay attention i'm using flayout navigation.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dani_S 3,316 Reputation points

2024-07-16T09:13:47.0366667+00:00

Your quick answer will be appreciated!
Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-16T09:24:28.07+00:00

Please see my updated answer.
Dani_S 3,316 Reputation points

2024-07-16T09:30:04.75+00:00

1.Does service locator with AddTransient for pages and viewmodel will solve the problem?
Dani_S 3,316 Reputation points

2024-07-16T09:31:55.66+00:00
2.and confirm with PG ??? about will page reuse in the Flyoutpage like the Maui Shell always re-uses pages

I do'nt understand what you want ?

Which code do you use to rproduce the bug?
Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-16T09:50:38.77+00:00

Does service locator with AddTransient for pages and viewmodel will solve the problem?

No, I tried it and set AddTransient for pages in my Flyoutpage demo, if I navigate to the other pages, the previous page still can find in the Managed Memory.

You can open an issue in the MAUI GitHub repo about these disappeared pages are still in the Managed Memory window.
Dani_S 3,316 Reputation points

2024-07-16T09:55:54.6466667+00:00

Does clear the navigation stack on disappering will solve the problem(with code suit to navigation)?

var stack = Shell.Current.Navigation.NavigationStack.ToArray(); for (int i = stack.Length - 1; i > 0; i--) { Shell.Current.Navigation.RemovePage(stack[i]); }
Dani_S 3,316 Reputation points

2024-07-16T10:02:06.28+00:00

Please add your demo in this bug:

https://github.com/dotnet/maui/issues/23625
Dani_S 3,316 Reputation points

2024-07-16T11:21:53.62+00:00

Your quick answer will be appreciated.
Dani_S 3,316 Reputation points

2024-07-17T06:56:57.39+00:00

Please add your demo in this bug:

https://github.com/dotnet/maui/issues/23625
Dani_S 3,316 Reputation points

2024-07-17T08:44:33.4166667+00:00

Please pass the demo before we close the thread.

Accepted answer

Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-17T06:54:16.74+00:00

Does clear the navigation stack on disappering will solve the problem(with code suit to navigation)?

var stack = Shell.Current.Navigation.NavigationStack.ToArray(); for (int i = stack.Length - 1; i > 0; i--) { Shell.Current.Navigation.RemovePage(stack[i]); }

You use FlyoutPage, why you use shell navigation? By the way, FlyoutPage is incompatible with .NET MAUI Shell apps, and an exception will be thrown if you attempt to use FlyoutPage in a Shell app. For more information about Shell apps.
Please sign in to rate this answer.

1 person found this answer helpful.
Leon Lu (Shanghai Wicresoft Co,.Ltd.) 71,936 Reputation points Microsoft Vendor

2024-07-17T09:03:45.0533333+00:00

@Dani_S I use this demo from the official FlyoutPageSample. Due to the policy, I cannot upload demo to the github, you can test it and update it by yourself.

Dani_S 3,316 Reputation points

2024-07-17T09:28:35.1233333+00:00

I did ,you can see in the github.
Sign in to comment

1 additional answer

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

flayout navigation - how to deal with rasing memory?

1 additional answer