Bug
The memory is not completely released by ArcGIS Runtime SDK for Java when adding and removing graphics from a GraphicsOverlay.
| Bug ID Number | BUG-000134864 |
|---|---|
| Submitted | October 23, 2020 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS Runtime SDK |
| Version found | 100.4 |
| Operating System | Windows OS |
| Operating System Version | 2008 R2 64 Bit |
| Status | Non-Reproducible |
Additional Information
Memory management in Java apps is not as simple as suggested in this scenario. If the user allocates a load of resources in a Java app then releases them, the user can’t expect an immediate drop in the memory footprint of the app running on their machine. This is not how memory is controlled in a managed environment like a Java Virtual Machine (JVM). The memory is released when the JVM decides it is time to perform a garbage collection. We have no control over this, the JVM does this in the background when it decides the time is right and cannot predict when it is going to happen. Forcing a garbage collection in code (which is exceedingly bad practice) does not even free up memory.Steps to Reproduce
Bug ID: BUG-000134864
Software:
- ArcGIS Runtime SDK
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App