ABSOLUTLY INSANE MEMOEY LEAKS, HELP!!!
I'm actually a bit confused as to the extent of the memory leaks in MAUI. Basically anything other than the default template page will cause a catastrophic memory leak, in which the page, the associated data and all the display elements will live rent free, forever in RAM. This is just insane!!!
For context, we are a company that published a productivity app for both IOS and Android back in 2019 with Xamarin RIP. It's quite the large app with GBs of data on display. We recently finished our transition to MAUI and we're facing abismal perf issues. After days of tracing and analyzing GC dumps, we've arrived at the following conclusion: for any large app, MAUI is basically an exercise in futility! How the hell did this framework get validated for prod i'm very confused?!!
Here's a small test app, with 3 basic pages, one is the control: the default page template. The second contains a basic CollectionView, the third a TitleView.
https://github.com/GUELIANEBelkacem/MySuperLeakyApp.git
Included in the repo is a gcdump of a simple nav to + back from the TitleView test page
Are we doing something wrong? what is happening? how does adding a TitleView with a label cause a catastrophic mem leak? oh don't event get me started on what happens when i add an event handler (my sample doesn't contain any). HEEELP!!!!
I'm going to submit an issue on the MAUI git, please tell me what you think and whether i'm missing something. Thank you kind strangers.
PS: shout out to u/scavos_official you sir are an angel, you have saved us days of GC analysis <3