| Numéro d’ID de bogue |
BUG-000110609 |
| Envoi | January 5, 2018 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Runtime SDK |
| Version trouvée | 100.2.0 |
| Système d’exploitation | SUSE Linux |
| Version du système d’exploitation | N/A |
| Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
This is working as expected. Memory usage does increase as more tasks are executed, but the memory is eventually freed. The tasks run slower in Debug mode, so this further exacerbates the issue and gives the impression that memory is not freed.
Here are a couple of ideas for capping the memory usage:
- Run the workflow synchronously. From our testing, there is not a noticeable performance hit than the async workflow and it caps memory usage.
- Put a limit on the number of async tasks being run concurrently. For example, only allow 10 or 20 async tasks to be run concurrently. The app developer can customize this to their liking to keep memory usage in check.
Solution de contournement
Wait for each fetchSymbol operation to complete before firing off the next request.
Étapes pour reproduire
ID de bogue: BUG-000110609
Logiciel: