| Numéro d’ID de bogue |
BUG-000173442 |
| Envoi | January 7, 2025 |
| Dernière modification | June 29, 2025 |
| S’applique à | ArcGIS Maps SDK for .NET |
| Version trouvée | 200.5 |
| Système d’exploitation | Apple iOS |
| Version du système d’exploitation | 16.x |
| Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
After looking into how GeoView behaves in your app and comparing it with the sample code, here’s what we have found:
Every time you hit Refresh, the app is pushing a brand new page onto the navigation stack.
The old pages (and their map views) are not being disposed of when this happens.
Because of this, each refresh leaves the previous map view in memory, even though you can’t see it anymore.
After 25–30 refreshes, the app ends up with 25–30 pages and map views still sitting in memory. This is what causes the memory usage to shoot up.
`await Shell.Current.Navigation.PushAsync(new MainPage(), false);`
This line creates a new MainPage every time but doesn’t remove the old one from memory. Since each page has a MapView, and those aren’t being disposed until the page itself is disposed, memory keeps growing.
This is not actually a bug in the GeoView or MapView. It is more about how the navigation is set up in your .NET MAUI app. The app keeps stacking up pages without cleaning up the old ones, which is why memory keeps increasing.
Solution de contournement
None.
Étapes pour reproduire
ID de bogue: BUG-000173442
Logiciel: