After upgrading to v12 from v10 we are seeing a significant amount number of jetsam events that are closing our application. We are running our test on an IPAD 6th gen with basically nothing else installed or running but our application. After relatively few view operations the jetsam logs get generated. I have duplicated a similar issue with the SQLite layer in the howDoI sample code – although it takes much more view operations before the app is closed. Our particular test case employs about 32 SQLite feature layers.
I added some simple memory tracking code into the application – managed memory appears very consistent between the v10 and v12, however the native memory is significantly different.
Taking a snapshot of mem usage prior to initial update the native memory usage in v10 is
After initial map update it is
Free Memory 78.66
For v12 mem usage prior to first update is
after initial map update it is
Free 18.27 MB
These numbers do represent the worse case scenario where all featues are visible. They are also numbers from when the app is built in debug. Only significant difference between the two versions is that one is using BingmapsLayers and the v12 version is using the overlay.
Numbers are relatively consistent over multiple runs. As mentioned the increased memory usage has proven to be significant problem which may forces us back to using v10 again.
v13.0-168 has introduced some redrawing issues over v13.0-167. When zooming in the map the display zooms immediately on the existing image that is displayed – the underlying features are redrawn and the old image is supposed to go away – that is no longer occurring the older enlarged feature display remains. Linear layers show this issue readily.
one piece of functionality that we have is the ability to zoom into a selected features bounding box. When we do this the base map goes away. Scale at bottom of the map indicates 50 feet for a frame of reference – v10 with bing layers does not have this issue.
When requesting a feature layer to be redrawn all features in the layer are getting refreshed instead of just the one. In this case all of the layers involved are in the same overlay.