Divesh,
Thank you.
No, that test case does not replicate the memory issue. After adding the AGSGraphicsLayer and adding the retrieved graphics to that layer, the test app's memory footprint increases about 25 mb. If you were to prevent the layer from drawing any graphics, you would see that the instantaneous memory increase from just adding the AGSGraphicsLayer is about 20 mb. I quickly hacked apart my original test case to show the cost of simply adding an empty AGSGraphicsLayer to an AGSMapView. Instead of switching between layer types, I just have a slider that sets the map to have between 0 and 20 empty AGSGraphicsLayers. Each empty graphics layer seems to cost about 20 mb, regardless of how many other layers are also on the map.
The memory usage increase I am seeing in my production app is obviously much higher. One thing that has occurred to me is that I am adding a custom drawing UIView on top of the map to allow the user to see in real time the freehand selection they are making. The custom UIView is not added directly onto the AGSMapView, but into the view containing the AGSMapView. This custom UIView draws a closed polygon in its layer in response to the user moving their finger. This is then converted to an identically symbolized AGSGraphic when the user is done with their gesture, the custom drawing UIView is dismissed, and the map returns to normal functioning. If the memory cost has to do with the map view adding each layer into rendering calculations even if it is empty, perhaps having an overlay over the map is increasing that memory cost.
