Maui - memory raising when using Application.Current.MainPage.Navigation.PushAsync

Question

Maui - memory raising when using Application.Current.MainPage.Navigation.PushAsync

Dani_S 5,581

Hi,

I used only Application.Current.MainPage.Navigation.PushAsync(new page) only in my app for navigationg but the memory is raising.

I tested with published as exe (from Visual studio 17.8.4).

https://app.screencast.com/cFXT6QgHXsVja

The structure of the app is describe in:

https://learn.microsoft.com/en-us/answers/questions/1607099/maui-using-timer-in-multi-main-page-navigations

Implementing a ContentView to change different layout over time

Thanks in advance,

Dani_S 5,581 Reputation points

2024-03-05T10:42:44.6333333+00:00

what i need to do in order the memeory will be stable.

Answer accepted by question author

1 additional answer

Your answer

Dani_S 5,581 Reputation points

2024-03-05T10:42:44.6333333+00:00

what i need to do in order the memeory will be stable.

Answer 1

Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,166 Microsoft External Staff

Hello,

For navigation, memory increases are expected behavior.

When you call the Application.Current.MainPage.Navigation.PushAsync(new page) method, a new page object is created and saved to the navigation stack. This results in an increase in memory usage.

These objects saved in the navigation stack will be released after being Popped, so generally speaking, this will not cause the user to occupy too much memory.

If you need to not increase memory when changing pages, you can use the replace current page instead of the navigation method.

Application.Current.MainPage = your page

Best Regards,

Alec Liu.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Dani_S 5,581 Reputation points

2024-03-06T09:54:45.5666667+00:00

Can you please look on the he structure of the app is describe in:

https://learn.microsoft.com/en-us/answers/questions/1607099/maui-using-timer-in-multi-main-page-navigations

Implementing a ContentView to change different layout over time

what i need to do in order to fix the memory leak.
Dani_S 5,581 Reputation points

2024-03-06T09:55:41.93+00:00

when i tried to call Application.Current.MainPage = your page is not working.
Dani_S 5,581 Reputation points

2024-03-06T10:02:25.57+00:00

" These objects saved in the navigation stack will be released after being Popped - i do not used it not work in my structte app,
Dani_S 5,581 Reputation points

2024-03-06T11:33:28.56+00:00

Can you please answer ?
Dani_S 5,581 Reputation points

2024-03-06T13:11:34.03+00:00

Another question this behavior of using

Application.Current.MainPage.Navigation.PushAsync(new page) only could lead to the crashed of I suffered?
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,166 Reputation points Microsoft External Staff

2024-03-07T01:23:45.14+00:00
Do you mean never calling the Pop method and always loading new pages into the navigation stack?

These objects saved in the navigation stack will be released after being Popped - i do not used it not work in my structte app,

If you only go in and out of the stack, your program in this case is actually an endless loop that will inevitably cause the program stack to overflow.

var list = new List<string>(); for (true) { list.Add("test"); }

Application.Current.MainPage.Navigation.PushAsync(new page) only could lead to the crashed of I suffered?

The problem is not Push, it's never to call PopAsync. For an app, there should generally be no more than five layers of navigation, and you can open your favorite app to confirm this. When the navigation starts, the program should not recycle the previous page.

For example, if the user navigates to the DetailsPage when changing the Details of an item in the list, how can the user see if the modification is successful? If it's an item in the middle of a very long list, the user will have to start from the home page, open the list page, and scroll to that item to see if the change is successful.

Saving a page to the navigation stack is actually a means of exchanging memory space for the convenience of the user, which contains the various states of the page. When a user falls back from DetaisPage all the way to the home page, the memory of the out-of-stack page is automatically released by the garbage collection mechanism.
Dani_S 5,581 Reputation points

2024-03-07T03:00:29.1066667+00:00

I open new thread asking how to solve it?

https://learn.microsoft.com/en-us/answers/questions/1610129/navigation
penygon user1 0 Reputation points

2024-06-05T11:33:36.7266667+00:00

Application.Current.MainPage = your page

How to use above code, please brief in detail

Answer 2

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

Maui - memory raising when using Application.Current.MainPage.Navigation.PushAsync

1 additional answer

Your answer